Global Master Data Sync

Global Master Data Sync is a master data management app for Microsoft Dynamics 365 Business Central that keeps shared reference data — items, customers, vendors, G/L accounts, dimensions, and more — consistent across multiple BC companies without manual re-entry or custom integrations. Where standard BC requires administrators to maintain the same master data separately in every company, Global Master Data Sync designates one company as the authoritative source (the Master) and automatically distributes approved data to any number of receiving companies (Subscribers) using a template-driven synchronization engine.

The app is built around three core concepts. Data Templates define what is synchronized: which BC table, which fields, which records (via filters), and which subscribers receive it. Partners represent the subscriber companies and determine how files are transferred — within the same tenant via a direct database connection, or across tenants via an External File Account or web service. Record Data is the live record set that tracks every synchronized record, its field values, and its synchronization status per subscriber. These three concepts work together: a released Data Template populates the record set automatically whenever source records change, packages the changes into IC files, and delivers them to each Partner.

Beyond the core sync engine, the app provides tools for every stage of the process: a Template Package library with ready-made templates for common data types (published by Abakion and downloadable with a single action), Partner Groups for managing many subscribers as a unit, a Subscriber Log for auditing every synchronization outcome, and an Obsolete Record handling mechanism that propagates deletions cleanly to subscribers. All processing runs in the background via Job Queue entries, requiring no manual intervention once the initial setup is complete.

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 BC company that participates in synchronization has a role set on the Global Master Setup page. A Master company owns Data Templates and distributes data. A Subscriber company receives and applies data. A Master and Subscriber company does both simultaneously — common in multi-tier group structures. The role determines which setup fields are visible, which automation flags apply, and which Job Queue entries are created.

Data Templates

A Data Template is the central configuration object. It defines one synchronization scope: one BC table, a selection of fields, optional record filters, optional fixed values, and a list of subscribers. Templates go through a lifecycle — Under Development (editable), Pending Approval (under review), Released (active, included in synchronization), and Obsolete (no longer distributed). Only released templates contribute to the record set and the IC file exchange.

Record Sets and IC Files

When a Data Template is released, the app builds a record set — an internal table that mirrors the source records and tracks their field values and synchronization status per subscriber. Whenever a source record changes (and Master Auto Update Record Set is enabled), the record set is updated automatically. At the next Job Queue run, changed records are packaged into IC File Logs and delivered to each Partner's file storage. The Subscriber's Job Queue then imports and applies the files to local BC records.

Transport Options

The Master and each Partner can exchange files in different ways. Database (same tenant) writes directly between companies — no file storage required. External File Account (default for cross-tenant) uses BC's built-in file account framework, supporting Azure Blob Storage, SharePoint, SFTP, and other connectors. Web Service (cross-tenant via OAuth 2.0) sends data directly to the subscriber's BC environment using Tenant Connector Codes. Azure Blob Storage (legacy) uses a direct SAS token connection and requires the hidden Use Original Blob Storage Setup flag to be enabled.

Job Queue

Synchronization is fully automated via two Job Queue entries created from the Global Master Setup page. The Master job creates and sends IC File Logs to subscribers on a 15-minute schedule. The Subscriber job imports received files and applies the data to local records. Both entries start in On Hold status and must be activated when ready. The entries are independent — a Master and Subscriber company runs both.

Typical Workflows

Setting up a new sync relationship

1. In the Master company, open Global Master Setup, set Company Type to Master, enter a unique Partner ID, configure the External File Account, and click Create Job Queue Entries.
2. Create one or more Data Templates — select the table, add fields, set filters, and release the template.
3. Create a Partner record for each subscriber company — set transport type, configure the file account or connection, and assign the relevant Data Templates.
4. In each Subscriber company, open Global Master Setup, set Company Type to Subscriber, enter a unique Partner ID, configure the same External File Account, and click Create Job Queue Entries.
5. Activate Job Queue entries in both companies.
6. Verify on the Global Master Record Data page that records are appearing and synchronizing.

Onboarding a new subscriber

1. In the Master company, create a new Partner record with the subscriber's Partner ID.
2. Assign the relevant Data Templates to the partner.
3. Run Transfer Record Data on the Partner card to push the full current record set to the new subscriber.
4. In the subscriber company, verify that records have been received and applied.

Adding Abakion standard templates

1. In the Master company, open Global Master Template Packages.
2. Click Get standard packages to download the latest library from Abakion.
3. Check Apply on the templates you want, then click Apply selected Packages.
4. Review and release the imported templates before the next sync run.

Investigating a sync failure

1. Open the Subscriber Log Entries page on the Subscriber company.
2. Filter to Errors and review the error message and record reference.
3. If the record is set to Skip Synchronization, investigate the root cause, fix the underlying data, and reset the synchronization attempt counter.
4. On the Master side, open Detail File Logs to verify that the file was sent and when.
5. On the Subscriber side, open Subscriber IC File Logs to verify that the file was received and processed.

Setup Checklist

Before going live with a sync relationship, verify:

• Both Master and Subscriber companies have the app installed and activated
• Global Master Setup is complete in both companies (Company Type, Partner ID, automation flags)
• An External File Account (or other transport) is configured and tested in both companies
• At least one Data Template has been created, configured, and released in the Master company
• Partner records exist in the Master company for each Subscriber, with templates assigned and the partner not on hold
• Job Queue entries are active in both companies
• The Subscriber Log Creation Policy is set to an appropriate level for production (Errors recommended)
• A test synchronization has been verified end-to-end in a sandbox environment

Integration with Other Abakion Apps