#10066 [PEPPOL] Handle unknown persisted PEPPOL format values
The PEPPOL 3.0 Format enum now handles persisted format values that become unknown when their declaring extension is uninstalled, preventing runtime errors and prompting users to select an available format.
- 3files
- 2AL files
- 2objects
Pull request · merged into main (BC30) on 2026-08-12 by djukicmilica · 3 files (+183 -0), 2 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Added unknown-value mappings for all interfaces implemented by the PEPPOL Format enum
- Created a handler that guides users to select an available format when encountering unknown formats
- Added test coverage for validation and conversion of persisted unknown ordinal values
- Behaviour changes for users or extensions.
AL objects touched
- Enum 37200 “PEPPOL 3.0 Format”, PEPPOL: modified
- Codeunit 37223 “PEPPOL30 Unknown Format”, PEPPOL: added
Context
- Work items: AB#646302
- Labels: AL: Apps (W1), Team: Integrations
- Systems: development
- From the description: “A PEPPOL format enum ordinal can remain in the persisted PEPPOL 3.0 Setup after the enum extension that declared it is uninstalled.”
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).