Recently, we ran into a few Flows in Power Automate where the trigger was failing whenever a filter criteria was defined in that trigger. The error details stated:
“Exception parsing aib_processingstatus eq 914700001 submitted for attribute filterexpression of callback registration. Target entity: aib_documentautomationprocessing. Exception: Microsoft.Crm.CrmInvalidOperationException: Unsupported AttributeType for AttributeTypeCode:FileType at Microsoft.Crm.ObjectModel.CallbackRegistrationTypeMapFactory.Get(AttributeMetadata attributeMetadata, EntityMetadata entityMetadata)
When we opened a ticket with Microsoft support, they suggested we remove the filter criteria and instead add a trigger condition.
To add a trigger condition, click the ellipses to display the trigger settings. Once the settings are displayed, you can add a trigger condition. In this example, we used the following expression:@equals(triggerOutputs()?[‘body/aib_processingstatus’],914700001
If you’d like to learn more about Power Automate, join us Oct. 6 for our free training: Sign up now.
