tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 6432 "E-Document Message"

EDocument · Microsoft.eServices.EDocument.Processing.Message

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 6 connected objects and pages

Table 6103 "E-Document Service" (relates to)E-Document ServiceTable 6121 "E-Document" (relates to)E-DocumentTable 6125 "E-Doc. Data Storage" (relates to)E-Doc. Data StorageCodeunit 6537 "E-Doc. Message Send Runner" (pages and codeunits on it)E-Doc. Message Send RunnerCodeunit 6538 "E-Doc. Message Resp. Runner" (pages and codeunits on it)E-Doc. Message Resp. RunnerPage 6434 "E-Document Messages FactBox" (pages and codeunits on it)E-Document Messages FactBox

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Caption E-Document Message
Access Internal

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Entry No. Integer — AutoIncrement; DataClassification SystemMetadata
2 E-Document Entry No. Integer — TableRelation Table 6121 “E-Document” (“E-Document”.“Entry No”); DataClassification SystemMetadata
3 Message Type Enum “E-Document Message Type” Specifies the type of the message, for example PEPPOL Order Response. via Page 6434 “E-Document Messages FactBox” enum Enum 6436 “E-Document Message Type”; DataClassification SystemMetadata
4 Direction Enum “E-Document Direction” Specifies whether the message was sent (Outgoing) or received (Incoming). via Page 6434 “E-Document Messages FactBox” enum Enum 6102 “E-Document Direction”; DataClassification SystemMetadata
5 Status Enum “E-Doc. Message Status” Specifies the current status of the message. via Page 6434 “E-Document Messages FactBox” enum Enum 6429 “E-Doc. Message Status”; DataClassification SystemMetadata
6 Data Storage Entry No. Integer — TableRelation Table 6125 “E-Doc. Data Storage” (“E-Doc. Data Storage”.“Entry No.”); DataClassification SystemMetadata
7 Created At DateTime Specifies when the message was created. via Page 6434 “E-Document Messages FactBox” DataClassification SystemMetadata
8 Response Type Enum “E-Doc. Response Type” Specifies the response type, for example Accepted or Rejected. via Page 6434 “E-Document Messages FactBox” enum Enum 6427 “E-Doc. Response Type”; DataClassification SystemMetadata
9 Service Code[20] — TableRelation Table 6103 “E-Document Service” (E-Document Service); DataClassification SystemMetadata
10 Last Attempt At DateTime Specifies when the service last attempted to send the message. via Page 6434 “E-Document Messages FactBox” DataClassification SystemMetadata
11 Retry Count Integer Specifies how many background send attempts have failed. via Page 6434 “E-Document Messages FactBox” DataClassification SystemMetadata
12 Last Error Text[2048] Specifies the error returned by the most recent failed send attempt. via Page 6434 “E-Document Messages FactBox” DataClassification CustomerContent
13 External Message ID Text[250] Specifies the identifier assigned to the message by the external service. via Page 6434 “E-Document Messages FactBox” DataClassification CustomerContent
14 External Document ID Text[250] — DataClassification CustomerContent
15 Received At DateTime Specifies when the external service created or delivered the incoming message. via Page 6434 “E-Document Messages FactBox” DataClassification SystemMetadata

Keys

  • PK: Entry No. (clustered)
  • EDocument: E-Document Entry No.
  • ExternalMessage: Service, External Message ID

Relations

Pages and codeunits on this table

Recent changes

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: "table", object_name: "E-Document Message"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources