Scheduling a Synchronization between Business Central and Dataverse

You can synchronize --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse records that have been previously coupled together. Or for records that are not already coupled, depending on the synchronization direction and rules, the synchronization jobs can create and couple new records in the destination system.

There are several synchronization jobs that are available out-of-the-box. The jobs are run in the following order to avoid coupling dependencies between tables. For more information, see Use Job Queues to Schedule Tasks.

1. CURRENCY - Common Data Service synchronization job.
2. VENDOR - Common Data Service synchronization job.
3. CONTACT - Common Data Service synchronization job.
4. CUSTOMER - Common Data Service synchronization job.
5. SALESPEOPLE - Common Data Service synchronization job.

You can view the jobs on the Job Queue Entries page. For more information, see Use Job Queues to Schedule Tasks.

Default Synchronization Job Queue Entries

The following table describes the default synchronization jobs for --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse.

| Job Queue Entry | Description | Direction | Integration Table Mapping | Default Synchronization Frequency (mins) | Default inactivity sleep time (mins) | |--|--|--|--|--|--|--| | CONTACT - Common Data Service synchronization job | Synchronizes Business Central contacts. | Bidirectional | CONTACT | 30 | 720
(12 hours) | | CURRENCY - Common Data Service synchronization job | Synchronizes --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse | CURRENCY | 30 | 720
(12 hrs) | | CUSTOMER - Common Data Service synchronization job | Synchronizes Business Central customers. | Bidirectional | CUSTOMER | 30 | 720
(12 hrs) | | VENDOR - Common Data Service synchronization job | Synchronizes Business Central customers. | Bidirectional | VENDOR | 30 | 720
(12 hrs) | | SALESPEOPLE - Common Data Service synchronization job | Synchronizes Business Central | SALESPEOPLE | 30 | 1440
(24 hrs) |

Synchronization Process

Each synchronization job queue entry uses a specific integration table mapping that specifies which --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse table to synchronize.

To synchronize data, Business Central when you are using the synchronization job queue entries. For more information, see Couple and Synchronize Records Manually.

• The Sync. Only Coupled Records check box controls whether new records are created when you synchronize. By default, the check box is selected, which means that only records that are coupled will be synchronized. In the integration table mapping, you can change the table mapping between a Business Central table so that the integration synchronization jobs will create new records in the destination database for each row in the source database that is not coupled. For more information, see Creating New Records.

  Example If you clear the Sync. Only Coupled Records check box, when you synchronize customers in --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse account that is not already coupled.

> [!NOTE]  
> There are rules and filters that determine what data is synchronized. For more information, see [Synchronization Rules](admin-synchronizing-business-central-and-sales.md).

• When new records are created in --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse depending on the synchronization direction. For more information, see Modify Table Mappings for Synchronization.

• With subsequent synchronizations, only records that have been modified or added after the last successful synchronization job for the table will be updated.

  New records in Business Central.

• With bidirectional synchronization, the job synchronizes from Business Central.

About Inactivity Timeouts

Some job queue entries, such as those that schedule synchronization between --- author: edupont04

ms.topic: include ms.date: 04/01/2021 ms.author: edupont

Dataverse, use the Inactivity Timeout field on the Job Queue Entry PAGE to prevent the job queue entry from running unnecessarily.