Page 9196 "Profile Import Diagnostics"
Base Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Environment.Configuration · captioned “Diagnostics” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Diagnostics |
| SourceTable | Designer Diagnostic |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| repeater | Severity | Severity | Specifies the severity of this diagnostics message. |
| Message | Message | Specifies the diagnostics message from the compiler. |
Relations
- source table Table 9175 “Designer Diagnostic”
Called by
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 9173 “Profile Helper” (1 call:
ShowProfileDiagnostics → (object)) - Page 9199 “Profile Import Wizard” (1 call:
OnInitializeStep → (object))
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: "page", object_name: "Profile Import Diagnostics"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.