Small and medium business | Business Central, N...

mdm

(4) Share

Report

Posted on by CD-12051622-0

Hello,

We are using Business Central Master Data Management to deploy new companies.

Our objective is to avoid manually recreating all setup and master data in each new company. We would like to use the standard synchronization framework to copy configuration tables from an existing company to newly created companies.

The process works for most tables, but when enabling synchronization on some mappings, we receive the following error:

"Data conflicts with the LinkTable and LinkFields settings in IntegrationFieldMapping."

Our understanding is that this error is related to the relationship defined between the source and destination tables, but we are not sure what specifically causes the conflict.

Our questions are:

Is using MDM synchronization the recommended approach to replicate setup/configuration tables into newly created companies?
Are there limitations regarding setup tables versus transactional tables?
What exactly triggers the "LinkTable and LinkFields" conflict in IntegrationFieldMapping?
Is there a recommended way to export/import table data between companies while preserving relationships and avoiding manual setup recreation?
Would RapidStart packages be a better approach than MDM synchronization for deploying configuration into new companies?

Our goal is simply to reuse existing setup and master data when creating new companies, instead of manually configuring everything again.

Thank you for your guidance.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Grigorios Mavrogeorgis 2,757 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

first thing — MDM is built for ongoing master data sync from a source company into subsidiaries, not really a one-time "stamp the setup into a new company" tool. If you just want to seed config once when a company is created, RapidStart configuration packages fit better, and they respect table relations and processing order. So on your fifth question, I'd lean RapidStart for pure deployment, MDM only if you want the new companies to stay linked to a master going forward.

Setup vs transactional — MDM is non-transactional only, don't put ledger or entry tables in there, even if they show in the list.
The LinkTable/LinkFields conflict I'm not certain on without seeing the mapping. My first guess is the field links to another table and that relation isn't resolving — maybe the related table isn't in the sync set, or the link fields don't line up. But that's a direction to check, not a definite cause. Open the failing field mapping and the LinkTable/LinkFields values should show what it expects.

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 18,309 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Hello,

For this scenario, I would treat MDM and RapidStart/configuration packages as two different tools: MDM is better for ongoing synchronization of non-transactional master data between companies, while RapidStart/configuration packages are usually better for initial company deployment/setup copy, especially when you want to copy setup tables in a controlled order. Microsoft also notes that MDM should not be used for transactional tables like ledger entries, and although setup/master tables can be synchronized, some tables are sensitive because they depend on other related tables/keys. The “LinkTable and LinkFields” error usually means the synchronization mapping/coupling cannot build a valid relationship between the records based on the linked table/fields, often due to missing related records, wrong mapping order, unsupported table relationship, or existing data that does not match the expected key/link structure. So for new company rollout, I would use configuration packages / copy data from company / RapidStart for the initial setup and master data load, then use MDM only for selected master data that must stay synchronized afterward, not as a general “copy everything” tool.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

AndrewThomas81 2,302 on at

Like
a
(1)

Report
Copy link

Link copied!

If you need ongoing sync use MDM, otherwise I would use config packs

My experiences with MDM to date have been very flakey!

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn

Was this reply helpful? Yes No

Join the conversation

Community site session details

mdm

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the June Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates