BC Observatoryunofficial, made by waldo
pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 20006 "APIV1 - Aut. Extension Upload"

APIV1 · Microsoft.API.V1

Open in Claude20006.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Table 5447 "API Extension Upload" (relates to)API Extension UploadCodeunit 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.

APIV1 · Microsoft.API.V1 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption ‘extensionUpload’, Locked = true
Extensible false
SourceTable API Extension Upload
PageType API

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
Group id Id —
content Content —

Triggers

OnFindRecord, OnOpenPage, OnModifyRecord

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: "APIV1 - Aut. Extension Upload"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources