In the light of the new API limits it’s good to let the Common Data Service (CDS) connector in Flow trigger only when it’s necessary. There are two options available to restrict the trigger: using Filtering attributes and/or Trigger Conditions.
Filtering attributes are available as an “advanced option” in the trigger of the CDS connector. Here I can put one or more attributes that will let…
Continue Reading StefanS365’s Article on their blog
Using Filtering attributes and Trigger Conditions to restrict trigger of CDS connector – There’s Something About Dynamics 365
Posted by In the light of the new API limits it’s good to let the Common Data Service (CDS) connector in Flow trigger only when it’s necessary. There are two options available to restrict the trigger: using Filtering attributes and/or Trigger Conditions. Filtering attributes are available as an “advanced option” in the trigger of the CDS connector.
Blog Syndicated with StefanS365’s Permission
More About This Author
Array
Dyn365CE2 February 2024Validate file input of manually triggered flow with trigger conditions
Dyn365CE25 October 2023Bulk Delete assets in Microsoft Purview via the user interface
Dyn365CE24 October 2023Bulk Delete assets in Microsoft Purview with Power Automate flow
Dyn365CE26 March 2023Populate a dynamic Microsoft Word template in Power Automate flow
