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

Table 6124 "E-Document Log"

EDocument · Microsoft.eServices.EDocument

Across versions

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

Neighbourhood 6 connected objects and pages

Table 6125 "E-Doc. Data Storage" (relates to, 2 links)E-Doc. Data StorageTable 6103 "E-Document Service" (relates to)E-Document ServiceTable 6121 "E-Document" (relates to)E-DocumentPage 6125 "E-Document Logs" (pages and codeunits on it)E-Document LogsCodeunit 6166 "EDoc Import PEPPOL BIS 3.0" (event subscribers)EDoc Import PEPPOL BIS 3.0Table 6123 "E-Doc. Mapping Log" (referenced by)E-Doc. Mapping Log

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 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
DataClassification CustomerContent
Permissions tabledata “E-Doc. Data Storage” = md

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 Specifies the log entry no. via Page 6125 “E-Document Logs” AutoIncrement
2 E-Doc. Entry No Integer — TableRelation Table 6121 “E-Document” (E-Document)
3 Service Code Code[20] Specifies the service code for the document. via Page 6125 “E-Document Logs” TableRelation Table 6103 “E-Document Service” (E-Document Service)
4 E-Doc. Data Storage Entry No. Integer Data Storage caption TableRelation Table 6125 “E-Doc. Data Storage” (E-Doc. Data Storage)
5 E-Doc. Data Storage Size Integer Specifies the file size of the document in bytes. via Page 6125 “E-Document Logs” FlowField: lookup(“E-Doc. Data Storage”.“Data Storage Size” where(“Entry No.” = field(“E-Doc. Data Storage Entry No.”)))
6 Status Enum “E-Document Service Status” Specifies the status of the document. via Page 6125 “E-Document Logs” enum Enum 6106 “E-Document Service Status”
7 Service Integration Enum “E-Document Integration” Specifies the integration code for the document. via Page 6125 “E-Document Logs” obsolete Pending 26.0; #if not CLEANSCHEMA29; enum E-Document Integration
8 Document Type Enum “E-Document Type” — enum Enum 6121 “E-Document Type”; not editable
9 Document No. Code[20] — not editable
10 Service Integration V2 Enum “Service Integration” Specifies the integration code for the document. via Page 6125 “E-Document Logs” enum Enum 6151 “Service Integration”
11 Document Format Enum “E-Document Format” Specifies the document format for the document. via Page 6125 “E-Document Logs” enum Enum 6101 “E-Document Format”; DataClassification SystemMetadata
12 Processing Status Enum “Import E-Doc. Proc. Status” Specifies the processing status of the document. via Page 6125 “E-Document Logs” enum Enum 6100 “Import E-Doc. Proc. Status”; not editable
13 Step Undone Boolean — not editable

Keys

  • Key1: Entry No. (clustered)
  • Key2: E-Doc. Entry No
  • Key3: Status, Service Code, Document Format, Service Integration
  • Key4: Status, Service Code, Document Format, Service Integration V2

Events published

Procedures

  • ExportDataStorage() (internal)
  • GetDataStorage(var TempBlob: Codeunit "Temp Blob"): Boolean (internal)
  • CanHaveMappingLogs(): Boolean (internal)

Plus 1 local procedures.

Triggers

OnDelete

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

Recent changes

Deprecations

  • field Service Integration: Pending 26.0 (#if not CLEANSCHEMA29), “Replaced by Service Integration V2.”

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

Evidence 1 sources