tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 46918 "BC14 Location"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Codeunit 46918 "BC14 Location Migrator" (pages and codeunits on it)BC14 Location Migrator

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.

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · captioned “Location Migration Data” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Location 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[10] —
2 Name Text[100] —
3 Address Text[100] —
4 Address 2 Text[50] —
5 City Text[30] —
7 Phone No. Text[30] —
11 Contact Text[100] —
35 Country/Region Code Code[10] —
54 Post Code Code[20] —
55 County Text[30] —
80 Use As In-Transit Boolean —
91 Require Receive Boolean —
92 Require Shipment Boolean —
93 Require Put-away Boolean —
94 Require Pick Boolean —
190 Bin Mandatory Boolean —

Keys

  • Key1: Code (clustered)

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

Evidence 1 sources