#9428 637301 Report layout override lifecycle
Report layout overrides for extension-installed layouts now write Tenant Report Layout Override records with lifecycle properties (status, description, obsolescence) scoped per field and per company, preserving existing company-level overrides while offering copy as an escape hatch.
- 6files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-08-17 by V-CWurtzen · 6 files (+982 -35), 3 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Status and Edit info changes on extension-installed layouts now write a Tenant Report Layout Override record instead of copying the layout
- Overrides apply to all companies by default; the former confirmation prompt is removed
- A company that already has its own status override keeps further status changes in that company; mixed-scope batch runs are rejected
- Scope is resolved per field, and only fields the user actually changed are written
- Save Changes to a Copy remains as an opt-in path; user-defined layouts are still updated in place
- Behaviour changes for users or extensions.
AL objects touched
- Page 9661 “Report Layout Edit Dialog”, Base Application: modified
- Page 9660 “Report Layouts”, Base Application: modified
- Codeunit 9660 “Report Layouts Impl.”, Base Application: modified
Context
- Work items: AB#637301
- Labels: Team: Integrations
- Systems: development
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).