Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Dual Write - "Pro...
Finance | Project Operations, Human Resources, ...
Suggested answer

Dual Write - "Project validation failed. [DIPV1034] Key field CustomerAccount in Customers V3 of AX must be mapped to a key field in accounts of CRM."

(0) ShareShare
ReportReport
Posted on by Phil Matthews 52

Good afternoon,

I'm setting up dual write between FO and CRM and I'm getting an error message when starting the mapping for Customers V3 (accounts):

Project validation failed. [DIPV1034] Key field CustomerAccount in Customers V3 of AX must be mapped to a key field in accounts of CRM.

The mapping version is the out of the box mapping, version 1.0.0.5. The CustomerAccount field is mapped to the Dataverse field accountnumber [Account Number]

Checking in Dataverse, I have a key set up including the Account Number and the Company (ie: the FO legal entity):

pastedimage1672767231926v1.png

I have refreshed all entities.

Does anyone have any suggestions as to why this error is occurring and how to resolve?

Thanks in advance.

  • RiVaVe Profile Picture
    RiVaVe 2 on at
    Dual Write - "Project validation failed. [DIPV1034] Key field CustomerAccount in Customers V3 of AX must be mapped to a key field in accounts of CRM."
    Hi Phil,
     
    I have a similar problem, but for me 'integration keys' does not seem available; if I click it, nothing happens. Do you maybe know what might be up?
     
    Thank you in advance
  • Suggested answer
    Phil Matthews Profile Picture
    Phil Matthews 52 on at
    RE: Dual Write - "Project validation failed. [DIPV1034] Key field CustomerAccount in Customers V3 of AX must be mapped to a key field in accounts of CRM."

    I have resolved this. The issue is that the Integration Key fields were incorrectly populated under Data Management > Dual Write > Integration Key. I deleted the fields from there and manually added the key fields that are shown in the screenshot in my initial post. The map then runs as expected.

    I'm unsure as to how the key came to be populated incorrectly, but there is another key listed against the Account Table in Dataverse with the fields that were originally listed, so I assume it just read that key first when setting up the Integration Key.

    pastedimage1672837303133v1.png

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.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey Pt 2

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,883 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,569 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans