Power Automate provides a standard solution to manage approvals in a Dataverse environment. Approval requests can be easily generated from cloud flows. Users have the ability to view and respond to approval requests from email, teams or the approval center which is accessible from the power automate website only.

Today, I will present a way to respond to approvals from a model driven app directly. Also, the approval requester will be able to cancel his request from the MDA in one click.

The approver can approve, reject, or assign the approval to a new approver in the organization:

The approval requestor can cancel his or her own approval request:

To implement this, we just need to use the widgets provided by the MsFlow js SDK. Yes, there is an SDK that allows us to generate some cool widgets. The approval center is one of them. Please refer to the documentation.

To enable Microsoft Teams in D365, Go to Settings –> Administration –> SystemSettings –> General Tab and flip the below highlighted options to Yes.

Once done, we’ll be able to see Collaborate button on the ribbon as shown below.

By default it’ll be enabled on several OOB entities as mentioned here: https://docs.microsoft.com/en-us/dynamics365/teams-integration/teams-collaboration#record-types-that-support-microsoft-teams-integration

However, we can also enable it on custom entity programmatically. Below is the screenshot of a custom entity “new_cidproduct” before enabling Teams integration on this entity.

We can use msdyn_SetTeamsDocumentStatusWeb API action to enable/disable Teams integration on a specific entity or a set of entities. Here, I have used my favorite Postman for the demo. Below are the request details:

Method: POST
URL: https://org.crm.dynamics.com/api/data/v9.0/msdyn_SetTeamsDocumentStatus
Body:
{
“Enable”:true,
“LogicalEntityNames”:”[“new_cidproduct”]”
}
Authorization: Configure the token to be passed along with the request.

Below is the screenshot of the request using Postman.

Once done with building…

I’m a huge fan of the Omni Channel Engagement Hub. You may have gathered this fact if you’ve read previous blogs, seen previous posts or watched me demo the product. I see the Omni Channel Engagement Hub as a game changer – it’s much easier to get up to speed with than it’s counterpart USD (Unified Service Desk) and it has so much more to offer than standard D365 Customer Service. Omni Channel was demoed at the recent Microsoft Business Applications Summit (if you missed it you can catch up on it here) and I hope this will have whet the appetite for more people to start looking into how they can adopt this product.

With that being said, Omnichannel is not perfect, there are some issues which I have faced and numerous people have also faced during their setup and configuration of OmniChannel. To hopefully make the future…