Table 327 "Tax Jurisdiction Translation"
Base Application · Microsoft.Finance.SalesTax
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Finance.SalesTax · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Tax Jurisdiction Translation |
| DataClassification | CustomerContent |
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 | Tax Jurisdiction Code | Code[10] | — | TableRelation Table 320 “Tax Jurisdiction” (Tax Jurisdiction); NotBlank |
| 2 | Language Code | Code[10] | — | TableRelation Table 8 “Language” |
| 3 | Description | Text[100] | — |
Keys
- Key1: Tax Jurisdiction Code, Language Code (clustered)
Relations
- Tax Jurisdiction Code: TableRelation Table 320 “Tax Jurisdiction”
- Language Code: TableRelation Table 8 “Language”
Countries that replace it
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). 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 Jurisdiction Translation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.