tableFinanceofficial - Microsoftderived - from the source, no model text

Table 20234 "Tax Attribute Value Mapping"

INTaxEngine · Microsoft.Finance.TaxEngine.TaxTypeHandler

Across versions

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

Neighbourhood 3 connected objects and pages

Table 20241 "Tax Attribute" (relates to)Tax AttributeTable 20242 "Tax Attribute Value" (relates to)Tax Attribute ValueCodeunit 20232 "Tax Type Object Helper" (calls)Tax Type 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.TaxTypeHandler · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Tax Attribute Value Mapping
Access Internal
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 Table ID Integer — DataClassification SystemMetadata
2 No. Code[20] —
3 Attribute ID Integer — TableRelation Table 20241 “Tax Attribute” (Tax Attribute); DataClassification SystemMetadata
4 Attribute Value ID Integer — TableRelation Table 20242 “Tax Attribute Value” (“Tax Attribute Value”.ID); DataClassification SystemMetadata

Keys

  • K0: Table ID, No., Attribute ID (clustered)
  • K1: Attribute ID, Attribute Value ID

Triggers

OnDelete

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: "table", object_name: "Tax Attribute Value Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources