Table 6125 "E-Doc. Data Storage"

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

Properties

Property	Value
DataClassification	CustomerContent

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
2	Data Storage	Blob	Specifies the binary data.
3	Data Storage Size	Integer	Specifies the size of the binary data.
4	Data Type	Integer	Specifies the file format of the binary data.	obsolete Removed 26.0; #if not CLEANSCHEMA26
5	Name	Text[256]	Specifies the name of the binary data.
6	Is Structured	Boolean	Specifies whether the binary data is structured and can be read.	obsolete Removed 26.0; #if not CLEANSCHEMA26
7	File Format	Enum “E-Doc. File Format”	Specifies the file format of the binary data.	enum Enum 6134 “E-Doc. File Format”

Keys

Key1: Entry No. (clustered)

Procedures

GetTempBlob(): Codeunit "Temp Blob"

Referenced by

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

Table 6121 “E-Document”: Structured Data Entry No., Unstructured Data Entry No.
Table 6124 “E-Document Log”: E-Doc. Data Storage Size, E-Doc. Data Storage Entry No.
Table 6432 “E-Document Message”: Data Storage Entry No.

Pages and codeunits on this table

Page 6111 “Inbound E-Doc. Picture” (source table)

Recent changes

2026-08-11 #9208 [Enforced Digital Vouchers] - Attaching EDocuments when using Digital Vouchers (main, BC30, feature)

Deprecations

field Data Type: Removed 26.0 (#if not CLEANSCHEMA26), “Use the File Format field instead.”
field Is Structured: Removed 26.0 (#if not CLEANSCHEMA26), “Unused, specified by the interface implemented by File Format.”

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