The Connector for Microsoft Dynamics supports mapping Microsoft Dynamics NAVentities, or record types, to their equivalent entities in Microsoft Dynamics CRM. For most data, synchronization occurs in only one direction, which is generally from Microsoft Dynamics NAV to Microsoft Dynamics CRM. This helps preserve data integrity in Microsoft Dynamics NAV, which is considered the system of record for most data that is exchanged. You can make changes in Microsoft Dynamics NAV and then synchronize the changes with Microsoft Dynamics CRM. However, for customers, contacts, and sales orders, the Connector for Microsoft Dynamics also provides maps that you can use to integrate data from Microsoft Dynamics CRM to Microsoft Dynamics NAV. For example, a salesperson can create a contact in Microsoft Dynamics CRM and then use synchronization to add that contact to the Microsoft Dynamics NAV database.
Standard Entity Mapping for the Connector for Microsoft Dynamics
The following table provides information about mapping and the synchronization direction for common entities. These maps are provided out-of-the-box. In addition, you can create custom maps that support your business processes.
| Microsoft Dynamics NAV entity | Connector source entity | Synchronization direction | Connector destination entity |
|---|---|---|---|
|
Customer |
NAV Customer Card |
Bidirectional |
Account |
|
Contact1 |
NAV Contact Card |
Bidirectional |
Contact |
|
Sales Order |
NAV Sales Order |
Bidirectional2 |
Order |
|
Sales Invoice |
NAV Sales Invoice |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Invoice |
|
Posted Sales Invoice |
NAV Posted Sales Invoice |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Invoice |
|
Item |
NAV Item Card |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Product |
|
Resource |
NAV Resource List |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Product |
|
Unit of Measure |
NAV Units of Measure |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Unit Group |
|
Salesperson/Purchaser |
NAV Salespeople/Purchasers |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
ERP System User |
|
Currency |
NAV Currency Exchange Rates |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Currency |
|
Payment Terms, Shipment Method, Shipping Agent |
NAV Enumerated Values |
Microsoft Dynamics NAV to Microsoft Dynamics CRM |
Picklist |
1You can only integrate contacts of the Type Person from Microsoft Dynamics NAV.
2 You can create a sales order in Microsoft Dynamics CRM, synchronize the information to Microsoft Dynamics NAV, and then synchronize back to Microsoft Dynamics CRM. However, after the sales order is considered submitted in Microsoft Dynamics CRM, you can only change and update the order in Microsoft Dynamics NAV.
 Important |
|---|
Because of data dependencies, we recommend that you activate
the maps in the following order. If you do not, then you will
likely encounter integration exceptions and warnings and may find
it difficult to troubleshoot synchronization errors:
|
Customized Entity Mapping
In most cases, you must customize the default mappings that are included with the Connector for Microsoft Dynamics to reflect how you use Microsoft Dynamics NAV and Microsoft Dynamics CRM. For example, if your entities include fields that are country/region-specific, then these fields are not included with the standard mappings. You must customize the mappings to account for these fields.
In another example, you may have a customized field in your Microsoft Dynamics CRM solution for which you want to provide synchronization. You must add this field to the relevant RoleTailored client page that is exposed as a web service. For example, if you want to have a CRM reference number on the Customer entity, then you must add the reference number field to the Customer Card page. The Connector for Microsoft Dynamics becomes aware of the field during configuration, and the field is exposed in the Connector for Microsoft Dynamics. You can then map it.
To add a custom field to standard entity maps
-
In Microsoft Dynamics NAV, in Object Designer, open the page that has been exposed as a web service in design mode.
-
Add the field to the page, and then recompile the page.
You may also want to provide an integration map for a custom entity. In this case, you must modify the IsIntegrationRecord function in the Integration Management codeunit to ensure that the OnDatabase<x> triggers are executed on the corresponding page or table. In this way, you can create integration records. You must also add the page as an integration web service. When you run the configuration tool in the Connector for Microsoft Dynamics, the fields are exposed to the Connector. You then create a map of the Microsoft Dynamics NAV fields to the equivalent Microsoft Dynamics CRM fields.