BC Observatoryunofficial, made by waldo
tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 46912 "BC14 Salesperson/Purchaser"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation

Open in Claude46912.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Codeunit 46912 "BC14 Salesp./Purch. Migrator" (pages and codeunits on it)BC14 Salesp./Purch. 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 “Salesperson/Purchaser Migration Data” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Salesperson/Purchaser 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 Name Text[50] —
3 Commission % Decimal —
5 Phone No. Text[30] — DataClassification EndUserIdentifiableInformation
7 E-Mail Text[80] Email caption DataClassification EndUserIdentifiableInformation
9 Job Title Text[100] —
10 Privacy Blocked Boolean —
11 Global Dimension 1 Code Code[20] —
12 Global Dimension 2 Code Code[20] —

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 Salesperson/Purchaser"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources