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

Table 725 "Custom Address Format"

Base Application · Microsoft.Foundation.Address

Across versions

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

Neighbourhood 4 connected objects and pages

Table 9 "Country/Region" (relates to)Country/RegionPage 725 "Custom Address Format" (pages and codeunits on it)Custom Address FormatPage 727 "Custom Address Format Factbox" (pages and codeunits on it)Custom Address Format FactboxCodeunit 9806 "Field Selection" (calls)Field Selection

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 Custom Address Format
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)
2 Line Position Option — OptionCaption: 1,2,3,4,5,6,7,8
3 Line Format Δ BC29 Text[80] Specifies address format fields.
4 Line No. Integer — AutoIncrement; DataClassification SystemMetadata
5 Field ID Δ BC29 Integer Specifies reference field ID. TableRelation Field.“No.” where(TableNo = const(79), “No.” = filter(2 | 3 | 4 | 5 | 6 | 30 | 31 | 36 | 51)); DataClassification SystemMetadata

Keys

  • Key1: Country/Region Code, Line No. (clustered)
  • Key2: Country/Region Code, Line Position

Procedures

  • BuildAddressFormat()
  • UseCounty(CountryCode: Code[10]): Boolean
  • ShowCustomAddressFormatLines()
  • MoveLine(MoveBy: Integer)
  • LookupField()

Plus 2 local procedures.

Triggers

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: "Custom Address Format"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources