enumIntegration & APIsofficial - Microsoftderived - from the source, no model textobsolete - pending
Enum 6104 "E-Document Structured Format"
EDocument · Microsoft.eServices.EDocument.Format
Across versionsobsolete pending since 26.0
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Format · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | true |
| ObsoleteState | Pending |
| ObsoleteTag | 26.0 |
| ObsoleteReason | Use “Structure Received E-Doc.” or “E-Doc. Read into Draft”. |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Azure Document Intelligence | Azure Document Intelligence | |
| 1 | PEPPOL BIS 3.0 | PEPPOL BIS 3.0 |
Deprecations
- object: Pending 26.0 (#if not CLEAN26), “Use “Structure Received E-Doc.” or “E-Doc. Read into Draft”.”
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: "enum", object_name: "E-Document Structured Format"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.