D365 F&O | Power Platform

 In this blog I am going to show another way of use the custom connector which went through in a previous blog. In this blog I am going to show how you can use PowerAutomate to Trigger a Approval/Verification flow which will use MS Teams for Approval. This does require the power platform integration to be switched on, that is widely documented on the MS Website and I imagine most newly provisioned environments will have this selected. Enable the Microsoft Power Platform integration - Finance & Operations | Dynamics 365 | Microsoft Docs The intention of this flow is when a new UK VAT number record is created, it triggers the API to go and verify if that number is correct then it will post a message to a channel in teams for a VAT team to approve they are happy with the number. This is just an example to highlight the way data events can be used to trigger external API's and approvals and it really open's the door for other opportunities. The first thing you want to do is cli...

When enabling data events in D365 F&O you might get some error which says similar to below: Exception while trying to get Virtual Entity metadata for entity: ##### I checked the logs and the following is showing depth is "Basic, BusinessUnitId" Response status code does not indicate success: 403 ({"error":{"code":"0x80040220","message":"SecLib::CheckPrivilege failed. User: #### , PrivilegeName: prvReadEntity, PrivilegeId: #### , Required Depth: Basic, BusinessUnitId: #### , MetadataCache Privileges Count: 5803, User Privileges Count: 82"}}). This means to resolve this make sure your application user in PowerPlatform admin center has the Basic user role.

 You may have seen this error when trying to deploy an environment  for D365 F&O with Dataverse integration  enabled. HttpError: [Bad Request], ErrorCode: [CdsProvisioningNotSupportedInLocation], ErrorMessage: [Currently, Dynamics 365 apps can only be enabled for your default region.], CDS correlation request id: [####]. In my case to fix it I deleted the environment and redeployed a new environment making sure the Azure AD region and region against the Azure Connector in the LCS project settings matched and this fixed the issue.