Table 286 "Territory"

Base Application · Microsoft.Inventory.Intrastat · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Territory
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	Code Δ BC28	Code[10]	Specifies a territory code.	NotBlank
2	Name Δ BC28	Text[50]	Specifies a description of the territory.

Keys

Key1: Code (clustered)

Relations

drill-down page Page 429 “Territories”
lookup page Page 429 “Territories”

Referenced by

8 fields in 8 objects relate to this table (TableRelation or CalcFormula).

Table 1381 “Customer Templ.”: Territory Code
Table 1383 “Vendor Templ.”: Territory Code
Table 18 “Customer”: Territory Code
Table 23 “Vendor”: Territory Code
Table 270 “Bank Account”: Territory Code
Table 5050 “Contact”: Territory Code
Table 5079 “Marketing Setup”: Default Territory Code
Table 5096 “Segment Wizard Filter”: Territory Code Filter

Pages and codeunits on this table

Page 429 “Territories” (source 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: "Territory"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 9 connected objects and pages