#11137 Composite Report Parts: seed via a report extension instead of install/upgrade code
The 14 shipped header/footer designs and report themes are now registered through a declarative Composite Layout report extension on Tenant Report Defaults instead of install/upgrade seeding code. The seeding codeunits, upgrade tag and SeedPart tests were removed, which also removes the elevated write path.
- 35files
- 8AL files
- 3objects
Pull request · merged into main (BC30) on 2026-09-15 by MSlenejennum · 35 files (+139 -869), 8 AL · refactor · tier official · reviewed (checked by Opus)
What changed
- Report extension replaces SeedPart-based install/upgrade code for seeding header/footer designs and themes
- Removes Composite Report Parts Mgt. codeunit, upgrade logic, and associated test suite
- Report part resources moved from .resources to Foundation/Reporting directory
- Platform now owns registering report extension layouts natively
- Eliminates permission-elevation issues from the previous approach
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 9998 “Upgrade Tag Definitions”, Base Application: modified
- Codeunit 5000 “BaseApp Install”, Base Application: modified
- Report extension 9666 “Composite Layout”, Base Application: added
src/Layers/W1/BaseApp/Foundation/Reporting/CompositeReportPartsMgt.Codeunit.al: removedsrc/Layers/W1/BaseApp/OtherCapabilities/Upgrade/UpgradeCompositeReportParts.Codeunit.al: removed
Also merged into
- #11128 into
releases/29.xon 2026-09-22
Context
- Work items: AB#649359
- Labels: Team: Integrations
- Systems: platform, 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).