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

Page 2011 "Entity Text Factbox Part"

System Application · System.Text

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 2012 "Entity Text Impl." (calls, 5 links)Entity Text Impl.Codeunit 2010 "Entity Text" (calls)Entity Text

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

Properties

Property Value
Caption Entity Text
Extensible false
SourceTable Entity Text
PageType CardPart
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
Entity Text EntityText Rec."Preview Text" —
EmptyCaption ComputedEmptyCaption —

Actions

Group Action ToolTip Runs
Processing Edit Open a dialog to edit the text
Draft with Copilot Let Copilot create a new draft

Procedures

  • SetContext(SourceTableId: Integer; SourceSystemId: Guid; SourceScenario: Enum "Entity Text Scenario"; PlaceholderText: Text): Sets the context for the Entity Text Factbox Part.

Plus 3 local procedures.

Triggers

OnInit, 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: "Entity Text Factbox Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources