People have been reporting that Dynamics 365 triggers in Flow are not consistent. Sometimes they fire twice, sometimes not at all, sometimes they fire after a manual test run. There are some other weird side-effects I did not even look into. Why? Because of one of them quick tips.
Where possible, use Common Data Service connector instead of Dynamics 365 one.
There is literally not much to add. Yes, CDS connector does have some functionality yet to be completed, hence “where possible” disclaimer.
Send your questions and comments either below or to @crmtipoftheday on Twitter.
I have a case open with Microsoft because of issues with the Dynamics 365 connector and they recommended to use CDS, however CDS is a premium connector.
that’s true but that only affects users on O365 Flow licenses. My bet is that eventually Dynamics 365 connector will go away. Just look at what happened to HTTP connector.
Thanks for your reply George, are you saying cds is included as part of Dynamics365 licencing then?
Either get them something more than team member or buy them a P1 or P2 powerapps license.
I found even the CDS trigger may run twice… checked Audit History of the record only being updated one.
Any resolution for this.
[…] 1227: Use CDS instead of Dynamics 365 connector in Flow […]