Update 29.0.202645.181856 (29.0)

Prev Next

Release Date: 4. November 2026

Release Summary


This release makes Global Master Data Sync easier to monitor, from inside Business Central and from external tools. It adds new read-only APIs for setup, sync status and templates, a Job Queue Activities cue on the Role Center, and a configurable threshold for when records not yet synchronized are highlighted. It also fixes field ownership protection after a failed synchronization.

New Feature


Monitor Global Master Data Sync from external tools

New read-only APIs let you follow synchronization across all your companies from tools such as Power BI or a monitoring dashboard. You can read the Role Center figures in one call, including records not yet synchronized grouped by age (0–4 hours, 4–24 hours, 24–72 hours, over 72 hours) and Global Master Data Sync job queue entries (total, in error, on hold). You can also list the individual records that are not synchronized, with error message, number of attempts and age. Data templates, template lines, sub templates, filters, fixed values and subscribers are also available through the APIs, so you can compare configuration between companies. In addition, the Role Center has a new Job Queue Activities cue, and on subscriber companies you can set how many hours a record may wait before the not-synchronized cue is highlighted.

Why it matters: You can spot sync backlogs, errors and configuration differences across companies in one place, without opening each company.

Bug Fixes


Field ownership protection re-enabled after a failed synchronization

Previously, if a synchronization to a subscriber company failed partway through, the user session that hit the failure could be left able to edit fields controlled by the master company, until the session was restarted. Protection is now switched back on as soon as the failure happens. This applies to synchronization run from the job queue as well as to actions such as Transfer Record Data on the Partner Card.

Why it matters: Master-controlled fields stay protected from local edits, even when a synchronization fails.