Devising a Synchronization Amidst Business Central and Dataverse

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.