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

Page 2509 "Extn Deployment Status Detail"

System Application · System.Apps

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 2503 "Extension Operation Impl" (calls, 2 links)Extension Operation Impl

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.Apps · captioned “Extension Installation Status Detail” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Extension Installation Status Detail
Extensible false
SourceTable NAV App Tenant Operation
PageType Card

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
Control16 App Name Name Specifies the name of the App.
App Publisher Publisher Specifies the name of the App Publisher.
App Version Version Specifies the version of the App.
Schedule DeploymentSchedule Specifies the deployment Schedule.
Started Date Rec."Started On" Specifies the Deployment start date.
Control17 Status Rec.Status Specifies the deployment status.
Summary DeploymentDetails Specifies the deployment summary details.
Control18 Details DetailedMessageLbl Specifies deploy operation details.
Error Details Detailed Message box DetailedMessageText Specifies detailed message box.

Actions

Group Action ToolTip Runs
Processing Refresh Refresh the deployment details.
Download Details Download the operation status details to a file.

Procedures

  • SetOperationRecord(NavAppTenantOperationRec: Record "NAV App Tenant Operation") (internal)

Plus 1 local procedures.

Triggers

OnAfterGetCurrRecord

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: "Extn Deployment Status Detail"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources