Table 1314 "User Tours"
Base Application · System.Environment.Configuration
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | User Tours |
| 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 | User ID | Text[132] | — | not editable; DataClassification EndUserIdentifiableInformation |
| 3 | Tour ID | Integer | — | |
| 4 | Status | Option | — | OptionCaption: None,Started,Completed,Expired |
| 5 | Version | Text[163] | — |
Keys
- Key1: User ID, Tour ID (clustered)
Procedures
AlreadyCompleted(TourID: Integer): BooleanMarkAsCompleted(TourID: Integer)
Plus 3 local procedures.
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 9015 “Application System Constants” (2 calls:
GetVersion → ApplicationBuild,GetVersion → ApplicationVersion)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "User Tours"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.