Table 1309 "O365 Getting Started"

Base Application · BC23-30 · source at ea08af5e · facts from BC29

Properties

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.

Keys

• Key1: User ID, Display Target (clustered)

Events published

• OnO365DemoCompanyInitialize() (integration)

Procedures

• AlreadyShown(): Boolean
• MarkAsShown()

Pages and codeunits on this table

• Page 1305 “O365 Developer Welcome” (source table)
• Page 1306 “O365 Tour Complete” (source table)
• Page 1307 “O365 Getting Started Device” (source table)
• Page 1309 “O365 Getting Started” (source table)

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 4030 “Client Type Management” (2 calls: AlreadyShown → GetCurrentClientType, MarkAsShown → GetCurrentClientType)

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: "O365 Getting Started"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.