Page 20002 "APIV1 - Aut. Extensions"
APIV1 · Microsoft.API.V1
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
APIV1 · Microsoft.API.V1 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | ‘extensions’, Locked = true |
| Extensible | false |
| SourceTable | Published Application |
| 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 | packageId | Rec."Package ID" |
— |
| id | Rec.ID |
— | |
| displayName | Rec.Name |
— | |
| publisher | Rec.Publisher |
— | |
| versionMajor | Rec."Version Major" |
— | |
| versionMinor | Rec."Version Minor" |
— | |
| versionBuild | Rec."Version Build" |
— | |
| versionRevision | Rec."Version Revision" |
— | |
| isInstalled | isExtensionInstalled |
— | |
| publishedAs | Rec."Published As" |
TODO(pteisolation) We should remove the code cop error for API pages |
Procedures
install(var ActionContext: WebServiceActionContext)uninstall(var ActionContext: WebServiceActionContext)
Triggers
OnAfterGetCurrRecord, OnOpenPage
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 2504 “Extension Management” (5 calls:
install → InstallExtension,install → IsInstalledByPackageId,OnAfterGetCurrRecord → IsInstalledByPackageId, …) - Codeunit 457 “Environment Information” (1 call:
OnOpenPage → IsSaaS)
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. Extensions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.