tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 11 "Country/Region Translation"

Base Application · Microsoft.Foundation.Address

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC292 fields changed
  5. BC30unchanged

Neighbourhood 3 connected objects and pages

Table 8 "Language" (relates to)LanguageTable 9 "Country/Region" (relates to)Country/RegionPage 80 "Country/Region Translations" (pages and codeunits on it)Country/Region Translations

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.

Base Application · Microsoft.Foundation.Address · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Country/Region 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 Country/Region Code Code[10] — TableRelation Table 9 “Country/Region” (Country/Region); NotBlank
2 Language Code Δ BC29 Code[10] Specifies the Language Code. TableRelation Table 8 “Language”
3 Name Δ BC29 Text[50] Specifies the translation of the name.

Keys

  • Key1: Country/Region Code, Language Code (clustered)

Relations

Pages and codeunits on this table

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: "Country/Region Translation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources