Table 2161 "Calendar Event User Config."
Base Application
Across versionsobsolete removed since 27.0
- BC23present
- BC24declaration changed
- BC25-26unchanged
- BC27declaration changed
- BC28-30unchanged
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Calendar Event User Config. |
| DataClassification | CustomerContent |
| ObsoleteState | Removed |
| ObsoleteTag | 27.0 |
| ObsoleteReason | Invoicing |
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 | User | Code[50] | — | DataClassification EndUserIdentifiableInformation |
| 2 | Default Execute Time | Time | — | |
| 3 | Current Job Queue Entry | Guid | — |
Keys
- Key1: User (clustered)
Deprecations
- object: Removed 27.0 (#if not CLEANSCHEMA27), “Invoicing”
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: "Calendar Event User Config."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.