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
- Dyn365CE20 May 2024Using BypassBusinessLogicExecution Parameter (Preview) to bypass Custom Sync and Async Logic (Plugin and Workflow) – Dataverse / Dynamics 365
- Dyn365CE16 May 2024Fixed – Dependency Calculation – There was an error calculating dependencies for this component. Missing component id {GUID} – Dataverse / Dynamics 365
- Dyn365CE15 May 2024Understanding Privilege Check and Shared Access in Dataverse / Dynamics 365
- Dyn365CE14 May 2024Turn on failed or You need a Microsoft Dynamics 365 license to continue error while trying to Activate a Workflow – Dynamics 365 / Dataverse