Dynamics 365 Triggers - No ODATA Filter?

[SAG_Toma]

Hi,

I have a few flows running that Connect to Dynamics 365 (Customer Engagment) using the Dynamics 365 triggers e.g.

 - When a record is created

 - When a record is updated

 - When a record is create or updated.

The Flows are running fine, however the trigger's have no ODATA filter options which means you get a very large amount of "Throw away" flow runs that simply don't need to run and get cancelled because they don't meet critera further into the flow. Does anyone know if there is a better solution for Flow trigger's in D365 (CRM)?

Thanks

Tom 

[LeeHarris · Accepted solution]

Hi @SAG_Toma 

If you create your Flow within a solution you should have access to the connector "Common Data Service (current environment)". This has a single trigger that can be configured to run when a record is created, created or updated, deleted, etc 

One of the options in this trigger is the "Filtering attributes". By providing the schema names for fields within the entity, the trigger will only fire if one of the defined properties is modified.

[SAG_Toma]

Ah OK, 

That's intresting, I had not thought of just by passing CRM and just going straight to CDS. Thanks for the tip!