#10604 [Main]-export/import of a report definition fails if the statuses in the originating company do not exist in the destination company
Financial report and row definitions now import successfully between companies even when the status codes do not exist in the destination company. The import process clears missing status references before applying the package, allowing the definitions to be imported with empty status fields.
- 10files
- 4AL files
- 1objects
Pull request · merged into main (BC30) on 2026-08-31 by DhavalMore88 (community contribution) · 10 files (+808 -0), 4 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added ClearNonExistingStatusInPackage procedure to handle missing status codes during import
- Prevents RapidStart package validation errors when status values don’t exist in destination company
- Clears non-matching status references while keeping row definitions and their lines intact
- Users can manually set status after import completes
- Added test coverage for missing statuses in multiple localizations (W1, APAC, CZ, ES, RU, SE)
- Behaviour changes for users or extensions.
AL objects touched
- Table 84 “Acc. Schedule Name”, Base Application: modified
Context
- Work items: AB#641481
- Labels: ADO: Sync, From Fork, Team: Finance
- Systems: finance
- From the description: “export/import of a report definition fails if the statuses in the originating company do not exist in the destination company”
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).