User Review( votes)
Microsoft Dynamics 365 pros share their tips on spotting trigger messages, handling HTTP requests, working with Citrix apps, and the role of change tracking.
Want to see your flow featured in a future edition of this series? Contact me with your example.
Spotting trigger messages with CDS connector for Power Automate
Older versions of Dynamics 365 Common Data Service connector offered separate triggers for each CRUD action like Create, Update, and Delete. But now the new version offers a single trigger. Writing in the Inogic Microsoft Dynamics 365 CRM Tips and Tricks blog, Roohi Shaikh explained what this means for Power Automate users. After the trigger is chosen, users can choose from different combinations of trigger conditions.
According to Shaikh, the new approach is more streamlined, allowing users to combine trigger conditions that were previously separate. Shaikh wrote:
In one of the projects we came across a scenario where in addition to the common logic to be executed for both Create and Update operation, there was one piece of logic specific to Update action. And there came the need to be able to identify the action that invoked the flow “Create” or “Update”. While the dynamic values listing does not provide this information directly, looking at the output body from the test execution, we found that it does share this information…
To add an expression, users can click on the fx button to bring up a new dialogue box where they can add-in dynamic values and a message name. Additionally, Shaikh noted the potential value of experimental features which can be accessed by navigating to Power Automate Settings.
Accepting and responding to HTTP requests
FREE Membership Required to View Full Content:
Learn more about us here