Monsieur Winner

MS D365FO || Monsieur D365FO

Technical

Account category or AX is a company-specific entity with primaryCompanyField set to DataAreaId and new_accountcategories of CRM is a cross-company entity that doesn’t have primary company field set. Please make sure the entities are both cross-company or company-specific entities.

Bonjour les amis.

Using dual write recently, we had cause to create custom entities on Both CE and FO.

While setting up the mapping , we got the error :

Account category or AX is a company-specific entity with primaryCompanyField set to DataAreaId and new_accountcategories of CRM is a cross-company entity that doesn’t have primary company field set. Please make sure the entities are both cross-company or company-specific entities.

This is simply because my custom table support cross company data sharing as stated in Microsoft documentation:

To resolve the error we can do the following:

1 . Go to Dataverse and add a new field (company) to our custom table.

2 . Add a new Key with Colum Company

 

and lastly

3 . Set the newly added field as an entity key on Dual write.

 

Voila!

Komi Siabi

Komi Siabi is a Bilingual D365FO Solution architect who loves sharing his knowledge as he works on Both Francophone and Anglophone projects around the globe. He enjoys doing some tiktok videos in his leisure time.

0 thoughts on “Account category or AX is a company-specific entity with primaryCompanyField set to DataAreaId and new_accountcategories of CRM is a cross-company entity that doesn’t have primary company field set. Please make sure the entities are both cross-company or company-specific entities.

Leave a Reply

Your email address will not be published. Required fields are marked *