I'm attempting to perform an initial sync for the dual write between Finance and Operations and Dataverse but I am getting this error and the initial sync doesn't run.
I have looked at my Company table in Dataverse and its values are all unique - which makes this error message confusing.
Can anyone please help:
Reason: Precondition Failed, Header x-ms-client-request-id 67c35655-9203-4c91-8aff-b3a1379a169a, A record that has the attribute values Company already exists. The entity key Company requires that this set of attributes contains unique values. Select unique values and try again.
Error message during Dual Write Initial Sync between D365 Finance and Operations and Dataverse
Hi, You can check out this document which mentions related issues regarding dual write for financial operations. The article mentions a similar issue as shown in the screenshot. You can also try re-running the initial sync. Sometimes the problem may be temporary and rerunning the sync may succeed. Troubleshoot live synchronization issues - Finance & Operations | Dynamics 365 | Microsoft Learn
Error message during Dual Write Initial Sync between D365 Finance and Operations and Dataverse
Hi,
The error message you're encountering indicates that there's a problem with uniqueness constraints in the Company entity during the initial sync between F&O and Dataverse. The error specifically states that a record with the attribute values for "Company" already exists, and the entity key "Company" requires that this set of attributes contains unique values.
Here are some steps you can take to address this issue:
Review Data in Finance and Operations: Ensure that in Dynamics 365 Finance and Operations, there are no duplicate records for the "Company" entity. Check if there are any records with identical attribute values.
Review Data in Dataverse: Double-check the Company table in Dataverse to confirm that all values are indeed unique. It's possible that there might be a data inconsistency or an issue with the uniqueness constraints.
Best regards,
Kevin
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.