Page 9197 "Profile Designer Diagnostics"
Base Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Profile Designer Diagnostics |
| SourceTable | Profile Designer Diagnostic |
| PageType | ListPart |
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 |
|---|---|---|---|
| Control1 | Profile ID | Profile ID | Specifies an ID that is used to identify the profile (role). There can be more than one profile with the same ID if they come from different extensions. |
| Message | Message | Indicates whether adding or replacing the profile was successful. Choose the link for more details. | |
| Source | ApplicationName |
Specifies the origin of this profile, which can be either an extension, shown by its name, or a custom profile created by a user. |
Procedures
SetRecords(ImportID: Guid)
Plus 1 local procedures.
Triggers
OnAfterGetRecord
Relations
- source table Table 9197 “Profile Designer Diagnostic”
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 2504 “Extension Management” (1 call:
OnAfterGetRecord → GetAppName)
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 Designer Diagnostics"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.