#11745 Bug 648781: check the party identifier that the PEPPOL export will use
PEPPOL validation now uses the same party identifier provider as export to ensure EndpointID is never empty, fixing cases where validation passed but export created invalid documents.
- 7files
- 5AL files
- 5objects
Pull request · merged into main (BC30) on 2026-09-25 by Explorer986 · 7 files (+543 -19), 5 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Validation now asks the same party info provider that export uses and checks that the EndpointID is not empty
- The provider is read from PEPPOL 3.0 Setup instead of being hardcoded, so SE can plug in its own provider
- Releasing a purchase order is now validated because a Purchase Header branch was added
- Reminders and finance charge memos get the same EndpointID check
- Documents that would have exported an empty EndpointID now fail validation, with a message that names the setting to change
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 6165 “EDoc PEPPOL BIS 3.0”, EDocument: modified
- Codeunit 6172 “E-Doc. PEPPOL Validation”, EDocument: modified
- Codeunit 37200 “PEPPOL30”, PEPPOL: modified
- Codeunit 37201 “PEPPOL30 Impl.”, PEPPOL: modified
- Codeunit 37203 “PEPPOL30 Sales Validation Impl”, PEPPOL: modified
Also merged into
- #12091 into
releases/29.xon 2026-09-30
Context
- Work items: AB#648781
- Labels: AL: Apps (W1), Team: Integrations
- Systems: development, integration
- From the description: “Validation now asks the same party info provider that export uses and just checks the answer is not empty.”
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).