Dynamics Community Forum Thread Details

mdm

Hello,

I am currently working on setting up MDM / Master Data Management synchronization in Business Central between one source company and several subscribed companies.

I will need to integrate a large number of synchronization tables. During my first tests, I encountered many errors such as:

The record already exists on several setup tables;
match-based coupling issues on Customer, Vendor, and Contact tables;
conflicts caused by data already existing in the destination company.

I would like to know the best practices to avoid as many synchronization/integration errors as possible before launching a large-scale synchronization.

For example:

Is it better to use an empty destination company or a pre-configured one?
Should synchronization tables be launched one by one at the beginning?
Should match-based coupling be configured before any synchronization?
What is the best way to handle records that already exist in the destination company?
What settings do you recommend for fields such as validation, overwrite local changes, create if not found, etc.?
Is it recommended to first test with only a few records before synchronizing all tables?