web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Project validation fai...
Finance | Project Operations, Human Resources, ...
Suggested answer

Project validation failed. AX key field FixedAssetNumber is not bi-directionally mapped to CRM key fields

(0) ShareShare
ReportReport
Posted on by Ruslan7 164

Hi All

I'm trying to set up dual-write for Fixed assets V2 entity and when I set up mapping for the FixedAssetNumber field I got this error

"Project validation failed. AX key field FixedAssetNumber is not bi-directionally mapped to CRM key fields"

I have checked the sync direction, it looks bi-directionally, also I have checked keys in dataverse FixedAssetNumber  is mandatory keys.

pastedimage1620334685987v1.png

What have I missed?

thanks 

Ruslan

I have the same question (0)
  • WillWU Profile Picture
    WillWU 22,361 on at
    RE: Project validation failed. AX key field FixedAssetNumber is not bi-directionally mapped to CRM key fields

    Hi Ruslan7,

    Did you define the FixedAssetNumber to an alternative key in Dataverse.

    docs.microsoft.com/.../enable-entity-map

    About defining alternate keys:

    docs.microsoft.com/.../define-alternate-keys-reference-records

  • Saurabh Pal Profile Picture
    Saurabh Pal 30 on at
    RE: Project validation failed. AX key field FixedAssetNumber is not bi-directionally mapped to CRM key fields

    Hi,

    Have you resolved this issue ? 

    Thanks,

    Saurabh

  • Suggested answer
    Haider241093 Profile Picture
    Haider241093 20 on at
    RE: Project validation failed. AX key field FixedAssetNumber is not bi-directionally mapped to CRM key fields

    If you are sure that integration keys are correct.

    Just from our experience, we were also getting this same error, but on different entity map- SalesOrderLine(CE)<->CDS sales order line V2(F&O). The thing which worked for us was changing the integration keys and then try to save the map(Hit & Try). It will again give error. Do this multiple times by changing the integration keys.

    And then change it back to the previous set of fields on Integration key.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 753

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 752 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 534 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans