Some out of the box standard Microsoft entity maps serve as prerequisites for few of the A365 entity maps. Before starting the A365 entity maps, we need to do a few things. 


The customers need to be running in order for some of the entities in the Device management solution to run.
Main entity 

  • Customer V3(accounts)

Other entities

  • Vendor payment method
  • Customer payment method
  • Currencies
  • Sales tax groups
  • Payment schedule
  • Payment days
  • Terms of payment
  • Vendor groups
  • Customer groups
  • Customers V3
  • CDS Contacts V2
  • Vendors V2
  • CDS Contacts V2

Begin by clicking the Customer V3 entity to enter the mapping details. When opening the entity map for the first time, integration keys on all related entities are populated. In the entity map, scan the mappings to verify that no mappings are missing or showing error message. 

After opening up the mapping details, go back to the list via the Dual write link (see screenshot below).

See instructions in the screenshot below
Select Customer V3 entity and press the Run button. 

  1. Flip the Show related table map(s) on. 
  2. Select Initial sync check box on the highlighted entities  
  3. Set the Master for initial sync as Finance and Operations apps 
  4. Press the Run button

Note: The arrows in point 2 and 3 indicate that the user should first select the Initial sync checkbox on all marked records before setting the Master for Initial sync. If you do Initial sync on one record and set the Master for initial sync to F&O and then go to the next record, then the F&O value is automatically set back to Common Data Service. There for Initial sync needs to be set for all appropriate records and then the Master for initial sync should be set for the same records. The same will apply for all remaining tasks in the document.

After running the initial sync wait until all entities in the list are with status Running. After that continue on to the next one. This could take a while (30-90 minutes), depending on the data.
If some entities fail e.g. the contacts, customers or vendors try running them again, and then without triggering the initial sync on related entities. Only run it for that particular entity. Sometimes the errors are due to sequencing and by running it again the issues are solved.


The Workers need to be running in order to sync responsible worker on the Service order.
Main entity:
Other entities:

Integration keys

After this we need to manually set one integration key for the User entity. 

Press the Integration key button and select the Integration key tab.

Find the User entity and press the Add key button. 

Select fullname field to be the integration key.
Press the Save button at the top and go back to the mapping list.