Page 9051 "Intercompany Setup Diagnostics"
Base Application · Microsoft.Intercompany.Setup
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Intercompany.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Intercompany Setup 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 |
|---|---|---|---|
| Issues Found | PartnerSetup | GetDiagnosticsErrorsCount(ICSetupDiagnostics.GetPartnerSetupId()) |
IC Partner Diagnostics |
| MappingSetup | GetDiagnosticsErrorsCount(ICSetupDiagnostics.GetMappingSetupId()) |
IC Mapping Diagnostics |
Procedures
4 local procedures, no public ones.
Triggers
OnInit
Relations
- source table Table 33 “Intercompany Setup 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 440 “IC Setup Diagnostics” (4 calls:
OnInit → InsertMappingSetupDiagnostics,OnInit → InsertPartnerSetupDiagnostics,SetupStyleExprs → GetMappingSetupId, …)
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: "Intercompany Setup Diagnostics"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.