Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
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
We recently encountered a client request to migrate orders from Dynamics 365 Customer Engagement to Finance and Operations on demand when the end user clicked a ribbon button. We had been leveraging the Prospect to Cash solution’s “Activate” button to simple set the Order to “Active” at which point the PowerApps data integrator would do the heavy lifting. This, however, took too long for certain use cases.
After looking at various options, we decided that leveraging Flow would give us the desired outcome and still leave the process within the D365 ecosystem and allow the customer easy access to modify the solution when needed.
At first, we tried using the Dynamics 365 “When Record is Updated” trigger, but we found the execution to be inconsistent because of the non-specific nature of the update step. So, we started looking at other methods to fire our Flow, and landed on the HTTP Request trigger.
As defined by Microsoft, the HTTP Request trigger is an incoming API call that can trigger the flow. Simply put, this trigger generates a URL the user can then put into whatever function they have to call this Flow on demand.
For our Flow, all we need to get is the GUID value of the order record. So, all we have to do is click “Use sample payload to generate schema,” and add a quick JSON snippet to generate our request schema:
Then, all we had to do was add some logic to dynamically pull the Order ID into the function. First, we give the function a name. In this case we named it “callFlow”. Then, we set a up a variable for the order ID using the Xrm.Page.data.entity.getId() method. The trouble here is that this returns the GUID with braces, which will break the JSON schema, so we have to add a quick snippet to strip the braces in the variable.
Click here to download the entire guide. Questions? Get in touch with us.
Business Applications communities