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

Table 9090 "Autocomplete Address"

Base Application · Microsoft.Foundation.Address

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Table 225 "Post Code" (relates to)Post Code

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 Autocomplete Address
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 Name Text[100] —
2 Address Text[100] —
3 Address 2 Text[50] —
4 City Text[30] —
5 Postcode Text[20] — TableRelation Table 225 “Post Code” (“Post Code” where(“Country/Region Code” = field(“Country / Region”)))
6 Country / Region Text[10] —
7 County Text[30] —
8 Id Integer —

Keys

  • Key1: Id (clustered)

Relations

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

Evidence 1 sources