Table 1307 "O365 Device Setup Instructions"
Base Application
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC261 fields removed
- BC27-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | O365 Device Setup Instructions |
| 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 | Key | Code[10] | — | |
| 11 | QR Code | BLOB | — |
Keys
- Key1: Key (clustered)
Procedures
GetActivationCode(): Text
Pages and codeunits on this table
- Page 1308 “O365 Device Setup” (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” (1 call:
GetActivationCode → 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 Device Setup Instructions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.