Recently in one of our flow triggers – When a row is modified (Dataverse), we got the below error Exception parsing _msdyn_billingaccount_value eq ‘a84c5028-ecdf-ed11-a7c7-00224893b2b0’ submitted for attribute filterexpression of callback registration. Target entity: msdyn_workorder. Exception: Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found…
Continue Reading Nishant Rana’s Article on their blog
Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)
Recently in one of our flow triggers – When a row is modified (Dataverse), we got the below error Exception parsing _msdyn_billingaccount_value eq ‘a84c5028-ecdf-ed11-a7c7-00224893b2b0’ submitted for attribute filterexpression of callback registration. Target entity: msdyn_workorder. Exception: Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE1 October 2024Using Microsoft Copilot Studio to create Copilot for Teams channel with Dataverse as Knowledge source – Copilot / Dataverse
Dyn365CE30 September 2024Use Copilot to generate knowledge articles from resolved cases – Dynamics 365 Customer Service
Dyn365CE24 September 2024How to remove contact and customer validation on Cases– Dynamics 365
Dyn365CE23 September 2024Use the new Associated Grid Control to display details of other tables in subgrids – Model-driven App / Dynamics 365
