Showing results for 
Search instead for 
Did you mean: 

Dynamics 365 > "When a record is updated" - provide information regarding which fields were updated

Alternatively, allow us to trigger a flow on the updating of a particular field.


Currently, when a Dynamics 365 record is updated, we have no useful information regarding the nature of the change. 



Status: New
Not applicable

I imagine that an array containing the names of changed fields would be sufficient. I don't know whether or not this is simple to implement.

Level: Power Up

Sounds like a nice to have feature.

Level: Powered On

It would be good if you could get the old value and the new value. Then you could use it in an email or push notification. Such as status for customer XXX changed from Active to Inactive or something like that.

Level: Powered On

would be awesome. Have been trying to do this with a flow from dynamics and a microsoft flow. But ran into the problem that processessions can`t be tracked 🙂 hope this feature will come soon.


And its already possible within dynamics with the workflows to start when a field is changed. So this must be possible in Microsoft Flow.

Level: Powered On

My blocker is a specific gap between the existing functionality in Dynamics 365 CRM Workflow and Plugins vs using the current version of the Dynamics/CDS connector for Flow.

  • In traditional Dynamics Workflow and Plugins, I can filter the firing of the event to only specific fields. (e.g. only fire if the customer status changes.) - Without this capability in the Flow connector for D365/CDS, the process fires multiple times whenever a record is touched - regardless of the need - and if the flow's objective is to update the record in dynamics, it results in an infinite loop.

  • The indiscriminate firing of the flow results in an excessively chatty process that restricts its usefulness. (e.g. if I'm paying for a 3rd party geocoding service that is only needed whenever an address is updated, I would be forced to pay for a huge amount of unnecessary usage since the service would be called repeatedly even when the address has not changed.)