Work or School Accounts Now Enabled in Community!
On May 12 Work or School Accounts were enabled in Community, along with Microsoft accounts (MSA). This allows seamless navigation between Community, Dynamics 365 applications, and Azure Active Directory enabled sites while logged into your Work or School account.
Read more | Managing Accounts
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
This is part 3 of the blog post series ‘Take Full Control over Your Flow Approvals‘ and in this part we’re going to create our own Flow to send the custom actionable message. The idea is to hook into the data of Approvals that is stored in the CDS for Apps and is created by the standard Approval actions in your environment(s). In the previous blog post I described the way we can create our own actionable messages for Approvals. We just need a Flow to send these, so let’s start with that. But first I need an Approval action.
I’ve created a Flow for the approval of a Credit Limit for an Account. Enable notifications is set to ‘No’.
Now let’s see what data is created once the Flow is run. The following Approval record is created and updated by the system.
And the next Approval Request record is created that is assigned to the approver (as Owner).
So our own Flow can/will be triggered when a Approval Request record is created, to send the custom actionable message to the approver(s).
We get the related Approval record and the details of the Requestor and Approver. The URL of the receiving Flow is set as value of the variable Flow URL. In the Compose action we add the HTML- and JSON code for the actionable message. The last action is to Send an email to the Approver and add the output of the Compose action into the Body of the email, and set ‘Is HTML’ to Yes.
Now if we start another Credit limit approval, the custom actionable message will be send to the approver(s).
This is the result.
The post Trigger your Flow on Approval Request to send the custom actionable message appeared first on There's Something About Dynamics 365.
Business Applications communities