Breaking news from around the world
Get the Bing + MSN extension
Answer forum questions for a chance to win prizesProviding verified answers in the community not only helps your colleagues find solutions, it also earns community members badges and spots on the Top 10 Leaderboards. Starting this month, your verified answers can help you earn a chance to win monthly prizes.
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
I’ve been using the Flow CDS connector for Dynamics and I think I have an issue with it. Don’t get me wrong, I can see its potential and I do like it but..
It seems that using the CDS on Updated of records and setting the advanced Attribute Filter to trigger the Flow on change of a specific attribute isn’t working quite the same as the traditional workflows in Dynamics.
Please correct me if I’m wrong but it looks like wherever the attribute is included in the update fields (even if it is unchanged), the Flow is being triggered, not just on change of the specified attribute.
Is this something anyone else has experienced?
Workflow engine works exactly the same. If entity's field is updated with the same value and field is listed in list of fields to trigger "Update" workflow - it will be triggered.
A flow will only trigger when your attributes have changed. This means within CDS or Dynamics if you update multiple fields at once ether through API or the web interface if you have a flow triggering off of one of those it will trigger.
Now the cool difference with Flow is they've recently added the ability for you to take this one step further and allow you to put conditions around when it executes. These are called "Trigger Conditions". This means for example if you wanted your flow to trigger off of the status reason field you could specify only when the status reason equals "In Progress". This is very different from the current Dynamics workflow engine where it triggers every time the field has changed.
There are some good videos made by the community out there showing this functionality off: powerusers.microsoft.com/.../334506
Business Applications communities