#11168 Restore E-Document vendor invoice field compatibility
E-Document vendor invoice field name restored from 'Applies-to Ext. Invoice No.' to 'Vendor Invoice No.' across handlers, tests, and documentation to maintain upgrade and extension compatibility.
- 15files
- 6AL files
- 6objects
Pull request · merged into main (BC30) on 2026-09-09 by djukicmilica (community contribution) · 15 files (+25 -21), 6 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Field 40 in E-Document Purchase Header renamed back to ‘Vendor Invoice No.’ for compatibility
- All APAC, DE, DK, ES, and FR handlers updated to use the restored field name
- Test cases and documentation aligned with the field name change
- Ensures existing extensions and translations continue to work
- Resolves upgrade compatibility issues introduced by the previous rename
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 11041 “E-Document ZUGFeRD Handler”, EDocumentDE (DE layer): modified
- Codeunit 13913 “E-Document OIOUBL Handler”, EDocumentFormatOIOUBL (DK layer): modified
- Codeunit 6404 “E-Doc. Create Purch. Cr. Memo”, EDocument: modified
- Page 6182 “E-Doc. Readable Purchase Doc.”, EDocument: modified
- Table 6100 “E-Document Purchase Header”, EDocument: modified
- Codeunit 6173 “E-Document PEPPOL Handler”, EDocument: modified
Context
- Work items: AB#649189
- Labels: ADO: Sync, AL: Apps (W1), From Fork, Ownership: Needs Review, Team: Other
- Systems: integration
- From the description: “Restores field 40 and W1 E-Document processing to use
Vendor Invoice No.”
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).