Synchronize data between Field Service and Business Central
When you want to synchronize data between Business Central and Field Service, you need to map the tables and fields in each application that stores the relevant data. This way, the data can be transferred and updated correctly. Mapping is done through special tables called integration tables. You can find more information about how to map tables and fields by visiting the Mapping the Tables and Fields to Synchronize page.
Standard synchronization tables
The integration with Field Service includes standard integration table mappings already set up for you:
PJLINE-WORDERPRODUCT- This mapping connects the work order products that you use in Field Service to track the materials used for a service order with the project journal lines that you use in Business Central to record the costs and revenues of a project.PJLINE-WORDERSERVICE- This mapping connects the work order services that you use in Field Service to track the labor hours and expenses for a service order with the project journal lines that you use in Business Central to record the costs and revenues of a project.PROJECTTASK- This mapping connects the projects and project tasks that you use in Business Central to plan and manage your service projects with the products in external projects that you use in Field Service to assign resources and tasks to a service order.RESOURCE-BOOKABLERSC- This mapping connects the resources that you use in Business Central to represent your service personnel, equipment, and tools with the bookable resources that you use in Field Service to schedule and dispatch them to service orders.SVCITEM-CUSTASSET- (Premium Experience only) This mapping connects the service items that you use in Business Central to track the warranty and maintenance information of your service products with the customer assets that you use in Field Service to store the service history and contract details of your service products.
Synchronization rules
An integration table mapping is a set of rules that define how data is exchanged between a table in Business Central and a table in Dataverse. These rules are important for ensuring that the integration synchronization jobs run smoothly and accurately, without losing or duplicating data.
One type of rule that you can specify in an integration table mapping is how to handle data conflicts that might arise when records are changed or deleted in one or both applications. For example, you can learn about some common rules for integrating with Sales by visiting the Synchronization Rules page.
Auto-resolve conflicts
Data conflicts are situations where the data in two business applications doesn't match because of changes or deletions that happened in one or both. Data conflicts can affect the quality and accuracy of data exchanged between the applications. Therefore, it's important to have a way to handle data conflicts when they occur. One way to handle data conflicts is to use resolution strategies that tell Business Central how to automatically resolve conflicts according to some predefined rules. This can save you time and effort by reducing the number of conflicts that you have to manually resolve.
Resolution strategies are part of the integration table mappings that define how data is synchronized between a table in Business Central and a table in Dataverse. You can specify different resolution strategies for different types of data conflicts. On the Integration Table Mapping page, you can see two columns that relate to resolution strategies: Resolve Deletion Conflicts and Resolve Update Conflicts. These columns let you choose how Business Central resolves conflicts that occur because records were deleted in one or both applications or updated in both.
In the Resolve Deletion Conflicts column, you can choose one of the following options:
Restore deleted records: This option tells Business Central to restore the records that were deleted in one of the applications, so that the data remains consistent in both applications.
Remove coupling: This option tells Business Central to remove the link between the records that were deleted in one of the applications, so that the data is no longer synchronized between the applications.
Do nothing: This option tells Business Central to ignore the deletion conflict and leave it for you to manually resolve.
If you select Do nothing, you have to go to the Coupled Data Synchronization Errors page and resolve the conflict manually.
In the Resolve Update Conflicts column, you can choose one of the following options:
Send update: This option tells Business Central to send the updated data from Business Central to Dataverse, overriding the data in Dataverse.
Get update: This option tells Business Central to get the updated data from Dataverse to update Business Central, overriding the data in Business Central.
Do nothing: This option tells Business Central to ignore the update conflict and leave it for you to manually resolve.
If you choose Do nothing, you have to go to the Coupled Data Synchronization Errors page and resolve the conflict manually.
After you specify the resolution strategy for each integration table mapping, you can use the Retry All action on the Coupled Data Synchronization Errors page to automatically resolve conflicts that match the strategy. This can help you keep data in sync between Business Central and Dataverse without having to manually intervene for every conflict.