Table 46901 "BC14 Post Code"
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Post Code Migration Data” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Post Code Migration Data |
| Extensible | false |
| 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 | Code[20] | — | |
| 2 | City | Text[30] | — | |
| 3 | Search City | Code[30] | — | |
| 4 | Country/Region Code | Code[10] | — | |
| 5 | County | Text[30] | — | |
| 6 | Time Zone | Text[180] | — |
Keys
- Key1: Code, City (clustered)
Pages and codeunits on this table
- Codeunit 46901 “BC14 Post Code Migrator” (codeunit runs on it)
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: "BC14 Post Code"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.