tableFinanceofficial - Microsoftderived - from the source, no model text

Table 20287 "Tax Table Relation"

INTaxEngine · Microsoft.Finance.TaxEngine.UseCaseBuilder

Across versions

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

Neighbourhood 4 connected objects and pages

Table 20306 "Tax Use Case" (relates to)Tax Use CasePage 20286 "Tax Table Relation Dialog" (pages and codeunits on it)Tax Table Relation DialogCodeunit 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 Table Relation
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 — TableRelation Table 20306 “Tax Use Case” (“Tax Use Case”.ID); DataClassification SystemMetadata
2 ID Guid — DataClassification SystemMetadata
5 Source ID Integer — DataClassification SystemMetadata
7 Table Filter ID Guid — DataClassification SystemMetadata
8 Is Current Record Boolean Specifies whether the attribute is mapped with the curent record of the use case. via Page 20286 “Tax Table Relation Dialog” DataClassification CustomerContent

Keys

  • K0: Case ID, ID (clustered)

Triggers

OnInsert, 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 Table Relation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources