Lazy Approvals for Dynamics 365 using Microsoft Flow

-

Lazy Approvals for Dynamics 365 using Microsoft Flow
I got a business requirement in Dynamics 365, where if  Opportunity discount % is greater than equal to 5, send an email to defined approver and get it approved on email only. This is to pace up the approval process without asking managers or Sr. Leaders to login to system. 
This was not possible earlier in Dynamics 365 however I have seen it happening in SharePoint using Nintex workflows.
This is now possible using Approvals in Microsoft Flow. Following is the solution and approach with pre-requisites.

      I had setup of the following environments with licenses appropriately.

a.       Microsoft Dynamics 365
b.       Microsoft Flow
c.       Microsoft Outlook – exchange license

Approach  :

Create following fields on Opportunity.
i.  Discount % - Whole Number
ii.  Approval status ( Option set with 3 values ie. Pending, Approved and Rejected).
iii.  Is email sent for approval? – Two Option

Create a new MS Flow on Dynamics 365 Opportunity update.




Add condition if Discount% is greater than or equal to 5, then check approval status should not be approved.



If condition is satisfied, Start Approval, as per the snapshot below.
Provide some details of the Opportunity in the email body or subject so that Approver can identify it from email itself. Once the user approves or rejects the opportunity, capture the response as Outcome with the comments in Dynamics 365.




Please note for approval response value in while capturing response will be Approve and Reject respectively.

If response is Approve, Update the opportunity record and set the correct values in respective fields as per the image below.





I have observed that flow triggered multiple times even after condition is failed. So to avoid that I have added one more condition just above start approval that If email is sent or not.


Cheers,
Javed Nehal Jamali




Comments

Post a Comment

Popular posts from this blog

Jenkins Setup for Salesforce.com Automated Deployment

-
Image
Continuous Integration (Build automation) for salesforce.com using GitHub repository: Step by Step by Jenkins Setup I did a small POC for Jenkins setup to automate the build deployment (Continuous Integration) of SFDC and GitHub as repository on cloud.  I thought to share my experience. To start with let’s first understand the basics and approach I took to achieve this. Following are the  major components are involved to make it happen. These are not software requirement. Software requirements are defined later in this article. 1.                   Salesforce instance – Source e.g.: Dev Sand Box where the configuration and customization has been done. 2.                   Eclipse with force.com IDE: This used to pull the desired code and components to be deployed at other Salesforce.com instance. 3.                   GitHub repository as source control 4.                   Jenkins : It control the deployment 5.                   Salesforce-Ant build tool
Read more

Cloud based CRMs (Dynamics CRM v.s. Salesforce) -Part 2

-
As promised in my last article (Part-1) here is the next version. You can find part-1 down below this page. Reports and Dashboards Microsoft had a pre-developed reporting engine within SQL Server called SQL Server Reporting Services (SSRS). Therefore, they made an understandable decision to use SSRS as the CRM reporting engine rather than creating CRM-specific. To utilize SQL and SSRS with in CRM, Microsoft built the integration between the CRM application and the SSRS. On the other hand, in absence of its own reporting engine Salesforce built its reporting engine from scratch and then leveraged this creation.  Salesforce reports don’t offer One-Click drill down. Salesforce reports has a lag of 30-60 minutes There were 25 types of pre-build reports are provided by Dynamics CRM. Simple to normal reports can be created by native report Wizard provided with in CRM. The complex reports can be created using SSRS and then it can be imported with in CRM. Microsoft CRM claims almost
Read more

Dynamics 365 Customer Engagement Queues and getting the best out it.

-
  If you are a Dynamics 365 Customer Engagement / Dynamics 365 CRM user and have doubts what the Queues are and why you should use Dynamics 365 Queues, keep reading to find out!   The Queues in Dynamics 365 Customer Engagement are frequently used to handle and route work items, such as when a customer service team is working on multiple projects and tasks simultaneously.   Case and Activities are 2 main entities enabled in the 'Services hub”.  3 out of the box views named as ‘Items available to work on’ or ‘Items I am working on’ and a ‘Tier 1 Queue’ provides all of the items that are available to be worked on and user may change as per the need and preference.   Queues can also be enabled for custom or out of the box tables. One important thing to be mindful while enabling the queues on tables tis that once Queue is enabled on a table, it cannot be disabled/reverted.   With the help of aforesaid views, you can “Pick” an item to show to other fellow team members
Read more