If you are managing multiple companies in a single BC environment you can use master data management (MDM) to sync your, as the name suggests, master data like Customers and Vendors.
Not every organisation needs to do that, but it's still worth remembering you can use the MDM feature to sync any table or field that's not posted data.
In the example below I show a simple setup to use MDM to sync key fields from the General Ledger Setup table - to manage the Allowed Posting Dates centrally.
As always lets check the docs Set up companies to synchronize master data - Business Central | Microsoft Learn here are the key steps from that page:
Quick Recap: Setting Up Data Sync in Business Central
Pull Model: The BC master data management tool allows you to pull data from a source company. Bi-directional sync is not possible out-of-the-box.
Integration Table Mappings: These define how data flows between Business Central and Dataverse. Predefined mappings exist for common entities (like customers and contacts), and you can customise or create new ones.
-
Coupling Records: Before synchronising, you need to couple (link) records so that the system knows they represent the same thing.
-
Job Queues: Use job queues to automate synchronisation. You can define how often data is pushed or pulled.
-
Manual vs. Automatic Sync: Some syncs happen automatically (via job queues), while others can be triggered manually, especially during setup or troubleshooting.
-
Managing Sync Errors: Business Central logs sync issues in the Integration Synchronisation Log, which helps diagnose and resolve problems.
Setup Steps
- Visit the Master Data Management page in the TARGET company [1]
- Select the correct SOURCE company [2]
- Don't enable yet [3]
- If you do it will import a default setup which we don't want in this case
- If you did enable it - you can access the Synchronisation Tables page and remove the ones you don't want.
- My preference is to have a clean slate, and only add the config tables we want.
- You can add by table number or name.
- Use the page inspection tool, on the page that has the data you want to sync, to check the table number for data on that page.
- In our case the table is 98
- Add this table in the Synchronisation Tables list page
- The tool will identify all the related tables - in other cases this is very handy - in our case we just want to sync the dates and keep the setup as clean as possible so I will say NO to these related tables.
- Next up picking the fields - I have selected the dates and set Overwrite Local Change - as we want the HQ company to set the value
- You can also set the overwrite at the table level - but I've left that off in this example
- With table 98 added and the field selected we can Enable Data Sync - it will offer to replace your setup with the default setup - say no to that!
- Finally we need to setup the match-based coupling - config tables are essentially a single row with a lot of columns - so we need to tell the MDM engine which field to match on - the Primary Key - naturally
- Lets check the job queue for the sync got created ok:
- Job looks look - its in the ready state. This will run periodically, the changes in the SOURCE company are not instant in the TARGET companies but happen periodically as this job runs. If you want to force a sync, you can click to run a foreground instance of the job.
- Lets check the sync logs
- 1 modified record which is as expected
Summary
What do you think?
Please let me know your thoughts in the comments
Connect or follow me on LinkedIn to get all my updates Andrew Wingate | LinkedIn
Click to Follow