Codeunit 6533 "E-Doc. Message Context"

EDocument · Microsoft.eServices.EDocument.Processing.Message · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• Initialize(EDocMessage: Record "E-Document Message"; TempBlob: Codeunit "Temp Blob") (internal)
• GetMessageEntryNo(): Integer: Gets the entry number of the child E-Document message being sent.
• GetMessageType(): Enum "E-Document Message Type": Gets the semantic type of the child E-Document message.
• GetResponseType(): Enum "E-Doc. Response Type": Gets the response type represented by the child message.
• GetTempBlob(): Codeunit "Temp Blob": Gets the message payload.
• Http(): Codeunit "Http Message State": Gets the HTTP state used to record the connector request and response.
• Status(): Codeunit "Integration Action Status": Gets the transport result. A connector must set the status to Sent or Pending Response after successful transmission.

Recent changes

• 2026-09-15 #10437 [FR E-Reporting] Add payment and invoice lifecycle messages (main, BC30, feature, added)

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. Message Context"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.