BC Observatoryunofficial, made by waldo
tableextensionIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table extension 7234 "MasterDataMgtFieldMapping"

MasterDataManagement · Microsoft.Integration.MDM

Open in Claude7234.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Table 5336 "Integration Field Mapping" (relates to)Integration Field Mapping

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.

MasterDataManagement · Microsoft.Integration.MDM · BC29-30 · source at ea08af5e · facts from BC29

Extends Integration Field Mapping.

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
7234 Overwrite Local Change Boolean Specifies if the synchronization should overwrite the local change that was done after the last synchronization. via Page 7236 “Master Data Synch. Fields”

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

Evidence 1 sources