Codeunit 6168 "E-Document Upgrade"
EDocument · Microsoft.eServices.EDocument
Across versions
- BC23-28not present
- BC29present
- BC30changed
EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Subtype | Upgrade |
Event subscriptions
- RegisterPerCompanyTags subscribes to Codeunit “Upgrade Tag” OnGetPerCompanyUpgradeTags
Procedures
GetUpgradeLogURLMaxLengthUpgradeTag(): Code[250](internal)GetUpgradeProcessDraftEnumTag(): Code[250](internal)GetUpgradeDataExchV2DefsTag(): Code[250](internal)GetEnableVATOptionsForPurchEDocTag(): Code[250](internal)
Plus 4 local procedures.
Triggers
OnUpgradePerCompany
Recent changes
- 2026-09-29 #11484 [E-Documents Core] - Supported type direction configuration (main, BC30, feature)
- 2026-09-15 #10437 [FR E-Reporting] Add payment and invoice lifecycle messages (main, BC30, feature)
Deprecations
- procedure UpgradeProcessDraftEnum: guarded (#if not CLEAN29)
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "E-Document Upgrade"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.