BC Observatoryunofficial, made by waldo
tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 9091 "Postcode Service Config"

Base Application · Microsoft.Foundation.Address

Open in Claude9091.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC261 fields changed
  5. BC27-30unchanged

Neighbourhood 1 connected objects and pages

Page 9143 "Postcode Configuration Page W1" (pages and codeunits on it)Postcode Configuration Page W1

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 Postcode Service Config
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 Primary Key Δ BC26 Code[10] —
2 ServiceKey Text[250] —

Keys

  • Key1: Primary Key (clustered)

Procedures

  • SaveServiceKey(ServiceKeyText: Text)
  • GetServiceKey(): Text

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

Evidence 1 sources