Table 2160 "Calendar Event"
Base Application
Across versionsobsolete removed since 27.0
- BC23present
- BC24declaration changed
- BC25unchanged
- BC26declaration changed
- BC272 procedures removed
- BC28-30unchanged
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Calendar Event |
| DataClassification | CustomerContent |
| Permissions | TableData “Calendar Event” = rimd |
| 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 | No. | Integer | — | AutoIncrement |
| 2 | Scheduled Date | Date | — | |
| 3 | Archived | Boolean | — | |
| 4 | Description | Text[100] | — | |
| 5 | Object ID to Run | Integer | — | |
| 6 | Record ID to Process | RecordID | — | |
| 7 | State | Option | — | OptionCaption: Queued,In Progress,Completed,Failed,On Hold |
| 8 | Result | Text[250] | — | |
| 9 | User | Code[50] | — | DataClassification EndUserIdentifiableInformation |
| 10 | Type | Option | — | OptionCaption: User,System |
Keys
- Key1: No. (clustered)
- Key2: Scheduled Date, Archived, User
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"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.