Release Date: 3. September 2026
Release Summary
This release lets subscriber companies request master data records directly from the master company, adds a clickable drilldown from template counts, fixes a sync error on long field values, and tidies up a few Partner Card details.
New Feature
Request master data records from a subscriber company
Record Selection now works in both directions. Previously only the master company could choose which records a subscriber received; now a subscriber company can browse and request specific records itself, for example an extra customer or item it needs. This requires "Exchange only Selected Records" to be enabled on the data template, and is available for G/L Account, Customer, Vendor, Item, Dimension Value, and Job/Project. Set up a connection to the master company under Global Master Data Sync Setup, then use "Request Master Records" from the relevant list.
Why it matters: Subscribers no longer have to ask the master company to add a missing record — they can request it themselves and get it synced back automatically.
Improvements
Drill down from the sub template count
The "Assigned Sub Templates" count on the data template card, and the "Assigned Subscribers" and "Assigned Sub Templates" counts on the data template list, are now clickable. Clicking a count opens the related records directly, instead of navigating through the actions menu.
Why it matters: Faster navigation from a template into its sub templates and subscribers.
Bug Fixes
Sync long field values without errors
Global Master Data Sync now handles field values up to 2,048 characters. Previously, if a synchronized field contained more than 250 characters — for example a long web address in the Vendor Homepage field — synchronization stopped with a length error and the record was not synced.
Why it matters: Records with longer field values, such as long URLs or notes, now sync correctly instead of failing.
Azure Blob Storage settings now shown only when relevant
On the Global Master Data Sync Partner Card, the Azure Blob Storage field group was previously always visible, regardless of which Data Exchange Type the partner used. It now appears only when the partner's Data Exchange Type is set to Azure Storage, so the card shows only the connection settings that apply.
Why it matters: Less clutter on the Partner Card — you only see the settings relevant to your setup.