tableFinanceofficial - Microsoftderived - from the source, no model text

Table 20286 "Tax Component Expr. Token"

INTaxEngine · Microsoft.Finance.TaxEngine.UseCaseBuilder

Across versions

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

Neighbourhood 4 connected objects and pages

Table 20285 "Tax Component Expression" (relates to)Tax Component ExpressionPage 20285 "Tax Component Expr. Subform" (pages and codeunits on it)Tax Component Expr. SubformCodeunit 20134 "Script Symbol Store" (calls, 2 links)Script Symbol StoreCodeunit 20141 "Lookup Entity Mgmt." (calls)Lookup Entity 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.

INTaxEngine · Microsoft.Finance.TaxEngine.UseCaseBuilder · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Tax Component Expr. Token
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 Component Expr. ID Guid — TableRelation Table 20285 “Tax Component Expression” (“Tax Component Expression”.ID WHERE(“Case ID” = Field(“Case ID”))); DataClassification SystemMetadata
4 Token Text[250] Specifies the Token name. via Page 20285 “Tax Component Expr. Subform”
5 Value Type Option — DataClassification SystemMetadata
6 Value Text[250] —
7 Lookup ID Guid — DataClassification SystemMetadata

Keys

  • K0: Case ID, Script ID, Component Expr. ID, Token (clustered)

Triggers

OnInsert, OnModify, OnDelete

Relations

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: "Tax Component Expr. Token"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources