Home
Blog
Business Central
Devising a Synchronization Amidst Business Central and Dataverse

Devising a Synchronization Amidst Business Central and Dataverse

Synchronizing Business Central and Dataverse.

Introduction

Imagine a scenario where you need to sync a huge table with 75000+ records of Business Central to the Dataverse. By default, each sync job has a timeout of 12 hours. You may increase it, but it is not the actual way to do it.

By a calculated measurement, 75K of records can be synced from Business Central to Dataverse for 12 hours. This time seems like the maximum that is taken to sync to the Dataverse.

To improve this time, we will look at how to sync Business Central and Dataverse and how that process can speed up through the latest Business Central updates.

Now synchronize Business Central with Dataverse on planned intervals by setting up jobs in the job queue. The synchronization jobs integrate data in Business Central and Dataverse records that have been earlier clubbed together.

For records that are not coupled the synchronization jobs can create and couple new records in the destination system depending on the synchronization direction and rules.

Several synchronization jobs are available out of the box. They run in the following order to avoid coupling dependencies between tables.

CURRENCY - Common Data Service synchronization job
VENDOR - Common Data Service synchronization job
CONTACT - Common Data Service synchronization job
CUSTOMER - Common Data Service synchronization job
SALESPEOPLE - Common Data Service synchronization job

Synchronization Process Overview

Each entry in the queue for a synchronization job defines the Business Central table and Dataverse table to synchronize using a unique integration table mapping. The table mappings additionally contain options that regulate which Dataverse and Business Central records should be synchronized.

For synchronization data, Dataverse table records should be coupled to Business Central records. For instance, a Business Central client should be coupled to a Dataverse account. This coupling can be set up manually before initiating the synchronization jobs. These jobs can be set up automatically as well.
The Sync. Only Coupled Records check box checks if new records are created when you synchronize. The check box is selected by default, which indicates that only records that are coupled will be synchronized.
In the integration table mapping, you can convert the table mapping between a Dataverse table and a Business Central table so that the integration synchronization jobs creates new records in the destination database for each row in the source database that is not coupled.

Find all details on this topic on Microsoft Learn. Contact us to know how our ERP integration services can expedite your business processes today.

Devising a Synchronization Amidst Business Central and Dataverse

Introduction

Synchronization Process Overview

Recent Posts

Business Central is defining the future of modern ERP software by incorporating powerful AI integrations.

DeepSeek vs. ChatGPT: A Technical Deep Dive

Use Raspberry Pi as an IoT Edge Device

GET A FREE QUOTE

Please fill this form and we'll get back to you as soon as possible!