Table 6107 "E-Documents Setup"
EDocument · Microsoft.eServices.EDocument
Across versionsobsolete pending since 28.0
- BC23-28not present
- BC29present
- BC30changed
EDocument · Microsoft.eServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | This table is obsolete and should not be used. |
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 | Id | Integer | — | AutoIncrement; DataClassification SystemMetadata |
| 2 | New E-Document Experience | Boolean | — | DataClassification CustomerContent |
Keys
- PK: Id (clustered)
Procedures
IsNewEDocumentExperienceActive(): BooleanGetListOfNewExperienceCountries(): List of [Text](internal)InsertNewExperienceSetup()(internal)
Plus 1 local procedures.
Recent changes
- 2026-09-30 #12070 Fix inconsistent CLEAN27/CLEAN28 tags in E-Document apps (main, BC30, fix)
Deprecations
- object: Pending 28.0 (#if not CLEANSCHEMA31), “This table is obsolete and should not be used.”
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-Documents Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.