Global Master Data Sync

Global Master Data Sync keeps reference data — items, customers, vendors, G/L accounts, and any other table you choose — consistent across multiple Microsoft Dynamics 365 Business Central companies or environments. Instead of maintaining the same master records by hand in every company, one company owns the data and the others receive it automatically, kept current as changes happen.

The app is built around a company-role model. Every participating company is assigned a role in Global Master Setup: a Master company owns the data templates and distributes their contents; a Subscriber company receives and applies that data; a company can also be Master and Subscriber at the same time, which is common when one company both distributes to subsidiaries and receives from a group-level parent. Data moves between companies using a transport the Master configures once — most installations use an External File Account (Business Central's built-in file connector framework, supporting SharePoint, Azure Blob Storage, SFTP, and others), with a legacy direct Azure Blob Storage option still available for existing installations. A direct web-service transport, authenticated via OAuth 2.0 Tenant Connector credentials, is also available for cross-tenant topologies that don't use shared file storage.

What data gets synchronized, and how, is defined in Data Templates — the Master decides which tables, fields, and filters to include, and which companies (individually or as Partner Groups) receive each template. Beyond the standard push model, a Subscriber can also actively request specific records it needs rather than waiting for the Master's scheduled distribution — useful when a Subscriber only needs a subset of the Master's data on demand. Every synchronization run is logged, giving administrators visibility into what was sent, what was received, and what failed.

Feature Map

Use this table to find the right article for your task.

Common Concepts

Several concepts appear across multiple articles. Understanding them once makes the rest easier to follow.

Company Roles

Every participating company has a Company Type: Master, Subscriber, or Master and Subscriber, set on the Global Master Setup page. This single choice determines which configuration groups and automation flags are relevant for that company.

Partner ID

Each company is identified to every other participant by a globally unique Partner ID, embedded in every file and record exchanged. It cannot be changed once Data Templates referencing it exist, so it should be planned before templates are released.

Transport

Data moves between companies using one of three mechanisms, configured on Global Master Setup: the External File Account (default for new installations, using Business Central's connector framework), legacy Azure Blob Storage (direct connection details, for existing installations), or a Web-service connection authenticated via a GM Tenant Connector Code for cross-tenant setups without shared storage.

Data Templates

A Data Template defines one synchronization scope: which table, which fields, and which filters apply. Templates are created and released on the Master, and assigned to Subscribers individually or via Partner Groups. Abakion publishes standard template packages for common scenarios that can be imported as a starting point.

Push and pull synchronization

The Master's scheduled Job Queue pipeline pushes record sets to Subscribers automatically. A Subscriber can also request specific records on demand rather than waiting for the next scheduled push, useful when only a subset of the Master's data is needed at a given moment.

Typical Workflows

Setting up a new synchronization relationship

1. On the Master company, open Global Master Setup, set Company Type to Master, and enter a unique Partner ID.
2. Configure the transport (External File Account is recommended for new installations) and create the Master's Job Queue entry.
3. Design or import a Data Template describing what should be synchronized.
4. On the Subscriber company, open Global Master Setup, set Company Type to Subscriber, enter its own unique Partner ID, and configure the same shared transport.
5. Create the Subscriber's Job Queue entry.
6. On the Master, add the Subscriber as a Partner (directly or via a Partner Group) and assign the Data Template.
7. Activate both Job Queue entries and confirm records flow through on the next scheduled run.

Daily synchronization (fully automated)

1. A tracked record is created, changed, or deleted on the Master.
2. The Master's record set is refreshed and packaged into an IC File Log for each relevant Partner.
3. The file is written to the shared transport.
4. The Subscriber's Job Queue picks up the file, unpacks it, and applies the changes to its own tables.
5. Successes and failures are written to the Subscriber Log according to the configured logging policy.

Troubleshooting a failed synchronization

1. On the Subscriber, review the Subscriber Log Entries filtered by partner and date, looking for failed records.
2. Check the record's synchronization attempt count against Maximum No. of Attempts to Synchronize — records that have exhausted their attempts are skipped until the automatic reset interval passes.
3. On the Master, use Show files (or the legacy Blob Storage equivalent) to confirm files are being written to the shared transport.
4. Fix the underlying issue (missing setup, filter mismatch, permission error) and allow the next scheduled run — or the automatic retry reset — to reprocess the record.

Setup Checklist

Before going live with a synchronization relationship, verify:

• Both companies have a Company Type and unique Partner ID set on Global Master Setup
• Both companies share a working transport (External File Account, legacy Blob Storage, or Web-service)
• At least one Data Template is released on the Master and assigned to the Subscriber (directly or via a Partner Group)
• Job Queue entries are created and activated on both Master and Subscriber
• A test synchronization has been verified end-to-end before going live in production

Integration with Other Abakion Apps