#12070 Fix inconsistent CLEAN27/CLEAN28 tags in E-Document apps
E-Document apps now use consistent CLEAN27 and CLEAN28 tags so each cleanup step can be removed independently, fixing compilation failures when only CLEAN27 was applied.
- 11files
- 7AL files
- 7objects
Pull request · merged into main (BC30) on 2026-09-30 by darjoo · 11 files (+59 -31), 7 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Moved references to ‘EDoc Historical Matching Setup’ from CLEAN28 to CLEAN27 guards since the table is removed in CLEAN27
- Updated Continia registration tests to use correct permission sets after ‘E-Doc. Core - Edit’ deletion in CLEAN27
- Added CLEAN27 guard to obsolete interface ‘IPurchaseLineAccountProvider’ to enable its future removal
- Reclassified ‘E-Documents Setup’ table as Removed in CLEAN28 and guarded its procedures
- Kept Purchase Header E-Document Link cleanup unguarded since import process version 1.0 is still supported
AL objects touched
- Permission set 6100 “E-Doc. Core - Objects”, EDocument: modified
- Permission set 6101 “E-Doc. Core - Read”, EDocument: modified
- Permission set 6105 “E-Doc. Core - User”, EDocument: modified
- Table 6121 “E-Document”, EDocument: modified
- Table 6107 “E-Documents Setup”, EDocument: modified
- Codeunit 6103 “E-Document Subscribers”, EDocument: modified
- Interface “IPurchaseLineAccountProvider”, EDocument: modified
Context
- Work items: AB#652070
- Labels: AL: Apps (W1), Team: Integrations
- Systems: integration
- From the description: “aligns the tags so each CLEAN step can be removed on its own”
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).