pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 8356 "MCP API Publisher Lookup"

System Application · System.MCP

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28unchanged
  4. BC29declaration changed
  5. BC30unchanged

Neighbourhood 2 connected objects and pages

Table 8350 "MCP API Publisher Group" (relates to)MCP API Publisher GroupCodeunit 8351 "MCP Config Implementation" (calls, 3 links)MCP Config Implementation

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.

System Application · System.MCP · captioned “API Groups” · BC27-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption API Groups
Extensible false
SourceTable MCP API Publisher Group
PageType List
ApplicationArea All

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 API Group API Group Specifies the API group.
API Publisher API Publisher Specifies the API publisher.

Relations

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.

Recent changes

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: "MCP API Publisher Lookup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources