The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
‘Better Together’ Integration forum available
We're launching a how-to forum where you can learn and engage about how Dynamics 365 integrates with other Power Platform products.
Read about Better Together forum
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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 the Flow trigger if they are changed. If I leave this blank the Flow will be triggered on change of any attribute.
But if I want to let the Flow trigger only when the record is Approved, I can set the Trigger Conditions in the settings of the trigger. You should use the Expression syntax here. You can add one or more conditions that will work as AND logical operator.
Now when the Approval field is updated, it will only trigger the Flow when the value is changed to Approved. This will save me some API requests.
The post Using Filtering attributes and Trigger Conditions to restrict trigger of CDS connector appeared first on There's Something About Dynamics 365.
Business Applications communities