pagePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Page 1446 "Headline RC Team Member"

Base Application · System.Visualization

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Page extension 1446 "Headlines RC Team Member Ext." (extended by)Headlines RC Team Member Ext.Codeunit 1440 "RC Headlines Page Common" (calls, 3 links)RC Headlines Page Common

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.Visualization · captioned “Headline” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Headline
PageType HeadlinePart

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
Control1 Greeting headline RCHeadlinesPageCommon.GetGreetingText() —
Control2 Documentation headline RCHeadlinesPageCommon.GetDocumentationText() —

Triggers

OnOpenPage

Extended by

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: "Headline RC Team Member"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources