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

Page 2504 "Extension Details Part"

System Application · System.Apps

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 2500 "Extension Installation Impl" (calls)Extension Installation 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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable Published Application
PageType CardPart
Permissions tabledata “Published Application” = r

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
Control2 Logo Rec.Logo Specifies the logo of the extension, such as the logo of the service provider.
Control9 Name Rec.Name Specifies the name of the extension.
Publisher Rec.Publisher Specifies the person or company that created the extension.
Version VersionDisplay Specifies the version of the extension.

Triggers

OnAfterGetRecord

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

Evidence 1 sources