BC Observatoryunofficial, made by waldo
pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 8366 "MCP API Version Lookup"

System Application · System.MCP

Open in Claude8366.mdSource on GitHub

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 8354 "MCP API Version" (relates to)MCP API VersionCodeunit 8351 "MCP Config Implementation" (calls)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 Versions” · BC28-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption API Versions
Extensible false
SourceTable MCP API Version
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 Version API Version Specifies the API version.

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.

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

Evidence 1 sources