#11517 [29.x]-export/import of a report definition fails if the statuses in the originating company do not exist in the destination company
Importing a financial report row definition (Acc. Schedule Name) into another company no longer fails when its Status code does not exist there. Before the package is applied, status codes missing in the destination company are blanked, so the definition imports with an empty status that the user can set later.
- 10files
- 4AL files
- 1objects
Pull request · merged into releases/29.x (BC29) on 2026-09-21 by DhavalMore88 (community contribution) · 10 files (+808 -0), 4 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added a procedure to clear non-existing status values from imported packages before applying them
- Status codes are company-specific and are not included in exports, causing validation failures
- Imported row definitions now accept empty status values that users can set after import
- Fixes import failure when destination company lacks financial report statuses from source company
- Added test cases across multiple localization layers to verify the fix
- Behaviour changes for users or extensions.
AL objects touched
- Table 84 “Acc. Schedule Name”, Base Application: modified
Context
- Work items: AB#650283
- Labels: ADO: Sync, From Fork, SCM, Team: Finance
- Systems: finance
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).