pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 9179 "Application Area"

Base Application · System.Environment.Configuration

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 9179 "Application Area Buffer" (relates to)Application Area BufferCodeunit 9178 "Application Area Mgmt." (calls, 2 links)Application Area Mgmt.

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.

Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Application Area
SourceTable Application Area Buffer
PageType List
UsageCategory Tasks
ApplicationArea All

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 Application Area Application Area Specifies the scope of the application functionality for which fields and actions are shown. Fields and action for non-selected application areas are hidden to simplify the user interface.
Show in User Interface Selected Specifies that fields and actions for the application area are shown in the user interface.

Procedures

1 local procedures, no public ones.

Triggers

OnModifyRecord, OnOpenPage, OnQueryClosePage

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

Evidence 1 sources