pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 9198 "Profile Import Result List"

Base Application · System.Environment.Configuration

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 9197 "Profile Designer Diagnostic" (relates to)Profile Designer DiagnosticCodeunit 2504 "Extension Management" (calls)Extension Management

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Environment.Configuration · captioned “Detailed Results” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Detailed Results
SourceTable Profile 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 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.
Severity Severity Specifies the severity of this diagnostics message.
Message Message Specifies the diagnostics message from the compiler.
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.

Triggers

OnAfterGetRecord

Relations

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.

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 Result List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources