Page 30007 "APIV2 - Aut. Extension Depl."
APIV2 · Microsoft.API.V2
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | NAV App Tenant Operation |
| 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 | Name | AppName |
— |
| Publisher | ExtensionPublisher |
— | |
| Operation Type | OperationTypeOption |
— | |
| Status | Rec.Status |
— | |
| Schedule | ExtensionSchedule |
— | |
| App Version | Version |
— | |
| Started On | Rec."Started On" |
— |
Triggers
OnAfterGetRecord, 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” (2 calls:
OnAfterGetRecord → GetDeployOperationInfo,OnAfterGetRecord → RefreshStatus)
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: "APIV2 - Aut. Extension Depl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.