Unanswered

Dataverse sync suddenly stopped working: "Failed to resolve entity metadata"

(0) Share

Report

Posted on by Bart van Tongeren

Hello all,

We have a bidirectional dataverse sync setup with Business Central. Everythings worked as expected and suddenly the sync stopped working.

Arround 2000 records are synced correctly and no errors are occuring. But the newly created records in BC are not synced correctly anymore to dataverse. The following error gets displayed for these records:

An error occurred while communicating with Dataverse.

Detailed description: One or more errors occurred. (Failed to resolve entity metadata for cr921_research.)

I have followed this article: https://yzhums.com/17065/

I do not have alot of error context, so I hope someone could help me out!

Thanks in advance and Kind Regards,

Bart van Tongeren

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

ELE365 2 on at

Like (0)

Report

Hi Bart,
did you find any solution? One of our customers is facing the same issue and it started to occur around the same time you posted this entry.

Was this reply helpful? Yes No
LorenzFl 2 on at

Like (0)

Report

Did you find any solution for this problem? Suddenly I get the same error with one of my customers.

Was this reply helpful? Yes No
Bart van Tongeren 27 on at

Like (0)

Report

Helllo all,

I managed to fix this issue by help of the following thread:
https://www.yammer.com/dynamicsnavdev/#/threads/show?threadId=2279280633389056&messageId=2279280633389056

The fix with "Coupled to CRM" field is completely unrelated. If you are seeing errors "Failed to resolve entity metadata", it means that you are missing a required privilege and the integration solution in your Dataverse environment needs to be upgraded to the version that has the additional privileges.
There are two ways to do this:
One way is:
to disable both Microsoft Dynamics 365 Connection Setup and Dataverse Connection Setup, then use the action "Redeploy Integration Solution" and reenable (first on "Dataverse Connection Setup" then do the same on "Microsoft Dynamics 365 Connection Setup").

Second way is:
If you don't want to disable and reenable, you can add the required privilege on PowerApps.
1. Follow this documentation https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges
to check the security role "Business Central Dataverse Integration" (for some users it is called "Business Central Cds Integration") in your Dataverse environment.
It must include organization level Read privilege for the Entity table and also for Attribute table. If it doesn't, then assign the required privileges and save the change. Entity and Attribute tables are under "Customizations" group of tables)
2. Once the role from step 1. has the prvReadEntity and prvReadAttribute privileges, make sure that the application user has this role assigned. Follow this to open user settings https://learn.microsoft.com/en-us/power-platform/admin/users-settings then choose "Application Users" and find the user with application id 88c57617-94ff-4043-a396-8a85a8d38922. This is the user that runs the integration with Business Central. It must have security role from step 1. assigned to it.
3. If the user doesn't have the required role, use https://learn.microsoft.com/en-us/power-platform/admin/assign-security-roles to make sure that security role from step 1. is assigned to this user.

What helped for me was to remove the dataverse setup in BC and reinstall it. And to remove the BC dataverse integration priviliges in Power Apps and to add them again afterwards.

I hope this will help you guys also.

Was this reply helpful? Yes No