pageFinanceofficial - Microsoftderived - from the source, no model text

Page 20172 "Action Loop Thr. Rec. Field"

INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 3 connected objects and pages

Table 20174 "Action Loop Through Rec. Field" (relates to)Action Loop Through Rec. FieldCodeunit 20133 "Script Symbols Mgmt." (calls, 2 links)Script Symbols Mgmt.Codeunit 20130 "App Object Helper" (calls)App Object Helper

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.

INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler · captioned “Mapping” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Mapping
SourceTable Action Loop Through Rec. Field
PageType ListPart

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 Field TableFieldName2 Specifies field name of the record.
Output Variable VariableName2 Specifies the variable name which will store the output.
Calculate Sum Calculate Sum Specifies if Tax Engine should store sum of the decimal values.

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetRecord, OnAfterGetCurrRecord

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: "Action Loop Thr. Rec. Field"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources