Mapping the Tables and Fields to Synchronize
The basis of synchronizing data is mapping the tables and fields in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse, so they can exchange the data. Mapping happens through integration tables.
Mapping Integration Tables
An integration table is a table in the Business Central.
When you create the connection between the apps, Business Central sets up some default mappings. You can change the table mappings if you want. For more information, see Standard Table Mapping for Synchronization. If you have changed the default mappings and want to revert your changes, on the Integration Table Mappings page, choose Use Default Synchronization Setup.
[!Note] If you are using an on-premises version of Business Central, the integration table mappings are stored in table 5335 Integration Table Mappings, where you can view and edit the mappings. Complex mappings and synchronization rules are defined in codeunit 5341.
Additional Mappings
Payment terms, shipment methods, and shipping agents can change, and it can be important to be able to adjust them. If you enable the Feature Update: Map to option sets in Dataverse without code feature on the Feature Management page, you can manually add integration table mappings for payment terms (PAYMENT TERMS), shipment methods (SHIPMENT METHOD), and shipping agents (SHIPPING AGENT). This mapping can help ensure that your policies are the same for these setups in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse.
Synchronization Rules
An integration table mapping also includes rules that control how integration synchronization jobs synchronize records in a --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse.
Strategies for Auto-Resolving Conflicts
Data conflicts can easily occur when business applications exchange data on an ongoing basis. For example, someone might delete or change a row in one of the applications, or both. To reduce the number of conflicts that you will have to manually resolve, you can specify resolution strategies and Business Central will automatically resolve conflicts according to the rules in the strategies.
Integration table mappings include rules that control how synchronization jobs synchronize records. On the Integration Table Mapping page, in the Resolve Deletion Conflicts and Resolve Update Conflicts columns, you can specify how Business Central will resolve conflicts that occur because records were deleted in tables in one or the other business application, or updated in both.
In the Resolve Deletion Conflicts column, you can choose to have Business Central automatically restore deleted records, remove the coupling between the records, or do nothing. If you do nothing, you must manually resolve conflicts.
In the Resolve Update Conflicts column, you can choose to have --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse, or do nothing. If you do nothing, you must manually resolve conflicts.
After you specify the strategy, on the Coupled Data Synchronization Errors page, you can choose the Retry All action to automatically resolve conflicts.
Mapping Integration Fields
Mapping tables is only the first step. You must also map the fields on the tables. Integration field mappings link fields in Business Central provides includes field mappings, but you can change those if you want. For more information, see Viewing Table Mappings.
[!Note] If you are using an on-premises version of Business Central, integration field mappings are defined in table 5336 Integration Field Mapping.
You can manually map the fields, or you can automate the process by mapping multiple fields at the same time based on criteria for matching their values. For more information, see To couple multiple records based on field value matching.
Handling Differences in Field Values
Sometimes the values in the fields that you want to map are different. For example, in Business Central it's "US." That means you must transform the value when you synchronize data. This happens through transformation rules that you define for the fields. You define transformation rules on the Integration Table Mappings page by choosing Mapping, and then Fields. Predefined rules are provided, but you can also create your own. For more information, see Transformation Rules.
Handling Missing Option Values in Mapping
Business Central table and added to the CDS Option Mapping system table to be handled manually later. For example, by adding the missing options in either product and then updating the mapping. For more information, see Handling Missing Option Values.
Coupling Records
Coupling links rows in Business Central. Coupling records offers the following benefits:
- It makes synchronization possible.
- Users can open records or rows in one business app from the other. This requires that the apps are already integrated.
Couplings can be set up automatically by using the synchronization jobs, or manually by editing the record in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse](admin-synchronizing-business-central-and-sales.md) and Couple and Synchronize Records Manually.
Filtering Records and Rows
If you do not want to synchronize all rows for a specific table in Business Central, you can set up filters to limit the data that is synchronized. You set up filters on the Integration Table Mappings page.
To filter records or rows for synchronization
Choose the
icon, enter Integration Table Mappings, and then choose the related link.To filter the Business Central records, set the Table Filter field.
To filter the --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse rows, set the Integration Table Filter field.
Creating New Records
By default, only records in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse) that is not already coupled.
For example, the SALESPEOPLE - Dynamics 365 Sales synchronization job uses the table mapping SALESPEOPLE. The synchronization job copies data from users in Business Central.
To create new records during synchronization
Choose the
icon, enter Integration Table Mappings, and then choose the related link.In the table mapping entry in the list, clear the Synch. Only Coupled Records field.
Use Configuration Templates on Table Mappings
You can assign configuration templates to table mappings to use for new records or rows that are created in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse rows.
If you install the default synchronization setup, most of the time, two configuration templates will be automatically created and used on the table mapping for Dynamics 365 Sales accounts: CDSCUST and CDSACCOUNT.
CDSCUST is used to create and synchronize new customers in Dynamics 365 Sales.
This template is created by copying an existing configuration template for customers in the application. The CDSCUST is created only if there is an existing configuration template and the Currency Code field in the template is blank. If a field in the configuration template contains a value, the value will be used instead of the value in the mapped column for the Business Central.
CDSACCOUNT creates and synchronizes new accounts in Business Central.
To specify configuration templates on a table mapping
Choose the
icon, enter Integration Table Mappings, and then choose the related link.In the table mapping entry in the list, in the Table Config Template Code field, choose to the configuration template to use for new records in Business Central.
Set the Int. Tbl. Config Template Code field to the configuration template to use for new records in --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse.
See Also
[About Integrating Dynamics 365 Business Central with --- author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse](admin-prepare-dynamics-365-for-sales-for-integration.md )
[Synchronizing Business Central and ---
author: edupont04
ms.topic: include ms.date: 04/01/2021 ms.author: edupont
Dataverse](admin-synchronizing-business-central-and-sales.md)
Schedule a Synchronization
--- author: edupont04