tableFinanceofficial - Microsoftderived - from the source, no model text

Table 20175 "Action Loop Through Records"

INTaxEngine · Microsoft.Finance.TaxEngine.ScriptHandler

Across versions

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

Neighbourhood 7 connected objects and pages

Table 20203 "Script Variable" (relates to, 2 links)Script VariableTable 20142 "Lookup Table Filter" (relates to)Lookup Table FilterTable 20143 "Lookup Table Sorting" (relates to)Lookup Table SortingPage 20171 "Action Loop Through Rec. Dlg" (pages and codeunits on it)Action Loop Through Rec. DlgCodeunit 20134 "Script Symbol Store" (calls, 3 links)Script Symbol StoreCodeunit 20141 "Lookup Entity Mgmt." (calls, 2 links)Lookup Entity Mgmt.Table 20174 "Action Loop Through Rec. Field" (referenced by)Action Loop Through Rec. Field

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 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Action Loop Through Records
Access Public
Extensible false
DataClassification EndUserIdentifiableInformation

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Case ID Guid — DataClassification SystemMetadata
2 Script ID Guid — DataClassification SystemMetadata
3 ID Guid — DataClassification SystemMetadata
4 Table ID Integer — TableRelation AllObj.“Object ID” where(“Object Type” = CONST(Table)); DataClassification SystemMetadata
5 Table Filter ID Guid — TableRelation Table 20142 “Lookup Table Filter” (“Lookup Table Filter”.ID where( “Case ID” = field(“Case ID”), “Script ID” = field(“Script ID”))); DataClassification SystemMetadata
6 Order Option Specifies ascending or descending order. via Page 20171 “Action Loop Through Rec. Dlg” DataClassification CustomerContent
7 Table Sorting ID Guid — TableRelation Table 20143 “Lookup Table Sorting” (“Lookup Table Sorting”.ID where( “Case ID” = field(“Case ID”), “Script ID” = field(“Script ID”))); DataClassification SystemMetadata
8 Distinct Boolean Specifies whether records will be distinct or not. via Page 20171 “Action Loop Through Rec. Dlg” DataClassification CustomerContent
9 Index Variable Integer — TableRelation Table 20203 “Script Variable” (“Script Variable”.ID where(“Script ID” = field(“Script ID”))); DataClassification SystemMetadata
10 Count Variable Integer — TableRelation Table 20203 “Script Variable” (“Script Variable”.ID where(“Script ID” = field(“Script ID”))); DataClassification SystemMetadata

Keys

  • K0: Case ID, Script ID, ID (clustered)

Procedures

  • DeleteFields()

Triggers

OnInsert, OnModify, OnDelete

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

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: "table", object_name: "Action Loop Through Records"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources