Page 7230 "Master Data Management Setup"
MasterDataManagement · Microsoft.Integration.MDM
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 7 connected objects and pages
MasterDataManagement · Microsoft.Integration.MDM · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Master Data Management Setup |
| SourceTable | Master Data Management Setup |
| UsageCategory | Administration |
| ApplicationArea | Suite |
| Permissions | tabledata “Master Data Management Setup” = rimd |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Connection | Company Name | Company Name | Specifies the name of the source company that you synchronize data from. |
| Source Environment Name | Source Environment Name | Specifies the source Business Central environment that master data is read from. Use the Cross-Environment Setup action to change it. | |
| Source Company Name | Source Company Name | Specifies the company in the source environment that master data is read from. Use the Cross-Environment Setup action to change it. | |
| Enable Data Synchronization | Is Enabled | Specifies whether data synchronization with the chosen source company. | |
| Delay Job Scheduling | Delay Job Scheduling | Specifies if the starting of the synchronization jobs should be delayed until a licensed user starts them explicitly from Job Queue Entries list. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Cross-environment setup | Set up the connection to a company in a different Business Central environment for cross-environment synchronization. | |
| Clear cross-environment setup | Remove the cross-environment connection - the source environment, company, and stored credentials - and return to same-environment synchronization. | ||
| Use default synchronization setup | Resets the synchronization tables, fields, and job queue entries to the default values for the connection with the source company. All current synchronization tables are deleted and recreated. | ||
| Export setup | Export the setup tables. | ||
| Import setup | Import the setup tables. | ||
| Start initial synchronization | Start all the default synchronization jobs for synchronizing data from the source company. Data is synchronized according to the mappings defined on the Synchronization Tables page. | Page 7234 “Master Data Full Synch. Review” | |
| Synchronize modified records | Synchronize records that have been modified since the last time they were synchronized. | ||
| Synch. job queue entries | View the job queue entries that manage the scheduled data synchronization. | ||
| Synchronization tables | View the list of tables to synchronize. |
Procedures
6 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnInit, OnOpenPage, OnQueryClosePage
Relations
- source table Table 7230 “Master Data Management Setup”
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 7233 “Master Data Management” (3 calls:
OnOpenPage → GetFeatureName,TryExportSetup → GetTelemetryCategory,TryImportSetup → GetTelemetryCategory) - Codeunit 457 “Environment Information” (1 call:
OnOpenPage → IsSaaSInfrastructure) - Codeunit 8703 “Feature Telemetry” (1 call:
OnOpenPage → LogUptake) - Codeunit 9179 “Application Area Mgmt. Facade” (1 call:
OnInit → CheckAppAreaOnlyBasic)
Recent changes
- 2026-10-02 #12196 [Master Data Management] Disable cross-env setup action OnPrem and fix field visibility issues (main, BC30, fix)
- 2026-09-22 #11626 [Master Data Management] Fixing synchronization of contacts, media, date, datetime, source watermarking, permission issue and minor UX issues (main, BC30, fix)
- 2026-09-10 #10753 Cross-environment Master Data synchronization (same tenant) (main, BC30, feature)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "page", object_name: "Master Data Management Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.