#11896 [Master Data Management] Cross-env over-cap blob clears the subsidiary blob
In cross-environment Master Data Management sync, a source blob over 512 KB is no longer sent inline, and now a skip marker keeps the existing destination blob instead of clearing it. The inline media cache now uses last-write-wins per record and field, so the newest media state is applied.
- 5files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-09-28 by dcenic · 5 files (+833 -3), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Source blobs over 512 KB are not sent inline, which previously cleared the destination blob
- A skip marker carried from materialization to transfer keeps the destination blob unchanged
- Inline media cache is last-write-wins per (SystemId, field) for records arriving on several pages in one batch
- Regression tests added for both cases
- Forward-port of a 29.x fix
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 7232 “MDM Inline Media”, MasterDataManagement: modified
- Codeunit 7248 “MDM Source Response”, MasterDataManagement: modified
- Codeunit 7237 “Master Data Mgt. Subscribers”, MasterDataManagement: modified
Context
- Work items: AB#651513
- Labels: AL: Apps (W1), Team: Finance
- Systems: integration
- From the description: “Carry a skip marker from materialization to transfer time and keep the destination blob unchanged.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).