Table 6122 "E-Doc. Service Supported Type"
EDocument · Microsoft.eServices.EDocument
Across versions
- BC23-28not present
- BC29present
- BC30changed
Neighbourhood 2 connected objects and pages
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 | E-Document Service Code | Code[20] | — | TableRelation Table 6103 “E-Document Service” (E-Document Service) |
| 2 | Source Document Type | Enum “E-Document Type” | Specifies the supported source document type. via Page 6129 “E-Doc Service Supported Types” | enum Enum 6121 “E-Document Type” |
Keys
- Key1: E-Document Service Code, Source Document Type (clustered)
Relations
- E-Document Service Code: TableRelation Table 6103 “E-Document Service”
Pages and codeunits on this table
- Page 6129 “E-Doc Service Supported Types” (source table)
Recent changes
- 2026-09-29 #11484 [E-Documents Core] - Supported type direction configuration (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: "table", object_name: "E-Doc. Service Supported Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.