Share
ReportHello,
I have two questions regarding MDM (Master Data Management) setup in Business Central, in a multi-company environment.
**Context:**
Our architecture works as follows:
- **OPERATIONS** is our parent/source company, centralizing all reference data for the group (customers, vendors, G/L accounts, posting groups, etc.).
- **PARAM** is a template company, already fully configured with all the MDM synchronization tables we need (match-based coupling, key fields selected, "Create if no match found" enabled). It serves as the base model for all new subsidiary companies.
- Each new **subsidiary company** (we need to set up around 10 to 15) is created by copying PARAM, then connected to OPERATIONS as its MDM source company.
- **OPERATIONS** is our parent/source company, centralizing all reference data for the group (customers, vendors, G/L accounts, posting groups, etc.).
- **PARAM** is a template company, already fully configured with all the MDM synchronization tables we need (match-based coupling, key fields selected, "Create if no match found" enabled). It serves as the base model for all new subsidiary companies.
- Each new **subsidiary company** (we need to set up around 10 to 15) is created by copying PARAM, then connected to OPERATIONS as its MDM source company.
**Question 1 — Automating MDM setup across multiple companies:**
Since we need to create around 10 to 15 subsidiary companies, doing the full MDM setup manually for each one is very time-consuming. Is there a way to automate or speed up this process, for example using RapidStart or a configuration export/import?
We already tried the native BC MDM configuration export (XML file) and imported it into another company, but it did not work as expected. Has anyone found a reliable way to replicate MDM configuration from one company to another without having to redo everything manually each time?
**Question 2 — Validation of our current procedure:**
For each new company created by copying PARAM, our current procedure is:
1. Copy PARAM to create the new subsidiary
2. Clean up irrelevant data in the new company (customers, vendors, posting groups that don't apply to this entity)
3. Set up filters on the synchronization tables (to only sync relevant data for this subsidiary)
4. Disable "Create if no match found" on all tables
5. Run the initial synchronization table by table (never "Start All" at once), starting with simple tables before more complex ones
6. Check the synchronization journal after each table (0 failures before moving to the next)
7. Re-enable "Create if no match found" table by table, only after confirming 0 failures
1. Copy PARAM to create the new subsidiary
2. Clean up irrelevant data in the new company (customers, vendors, posting groups that don't apply to this entity)
3. Set up filters on the synchronization tables (to only sync relevant data for this subsidiary)
4. Disable "Create if no match found" on all tables
5. Run the initial synchronization table by table (never "Start All" at once), starting with simple tables before more complex ones
6. Check the synchronization journal after each table (0 failures before moving to the next)
7. Re-enable "Create if no match found" table by table, only after confirming 0 failures
Is this the correct approach? Any best practices or improvements you would recommend?
Thank you in advance for your help.
Categories:
I have the same question (0)
All responses (
Answers (
673
