Codeunit 6116 "E-Doc. Unspecified Impl."
EDocument · Microsoft.eServices.EDocument.Processing.Import
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
ApplyDraftToBC(EDocument: Record "E-Document"; EDocImportParameters: Record "E-Doc. Import Parameters"): RecordIdRevertDraftActions(EDocument: Record "E-Document")StructureReceivedEDocument(EDocumentDataStorage: Record "E-Doc. Data Storage"): Interface IStructuredDataTypeReadIntoDraft(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob"): Enum "E-Doc. Process Draft"View(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob")GetResponseMessageType(EDocument: Record "E-Document"): Enum "E-Document Message Type"BuildMessage(EDocument: Record "E-Document"; ResponseType: Enum "E-Doc. Response Type"; var TempBlob: Codeunit "Temp Blob")FileExtension(): TextPreviewContent(FileName: Text; TempBlob: Codeunit "Temp Blob")PreferredStructureDataImplementation(): Enum "Structure Received E-Doc."
Recent changes
- 2026-07-27 #8698 [E-Documents Core] [Peppol] - Enabling EDI capabilities with E-Documents. PEPPOL Order Response Message Handling (main, BC30, feature)
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-Doc. Unspecified Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.