Codeunit 7245 "MDM Cross-Env Change Detector"

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

Properties

Property	Value
Access	Internal
Permissions	tabledata “Master Data Management Setup” = r, tabledata “Integration Table Mapping” = r, tabledata “Job Queue Entry” = rm, tabledata “Scheduled Task” = r

Events published

OnBeforeRescheduleSynchJob(var JobQueueEntry: Record "Job Queue Entry"; IntegrationTableMapping: Record "Integration Table Mapping"; var IsHandled: Boolean) (internal)

Procedures

DetectChanges() (internal)

Plus 14 local procedures.

Triggers

OnRun

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” (2 calls: DetectChanges → GetTelemetryCategory, ProcessDetectionResponse → GetTelemetryCategory)
Codeunit 7248 “MDM Source Response” (2 calls: DetectChanges → TryParse, ProcessDetectionResponse → ConsentRequired)
Codeunit 7244 “MDM Source Connection” (1 call: DetectChanges → GetTransport)
Codeunit 7246 “MDM Source Capabilities” (1 call: TryNegotiateDetectionSupport → IsSupported)

Recent changes

2026-09-10 #10753 Cross-environment Master Data synchronization (same tenant) (main, BC30, feature, added)

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: "codeunit", object_name: "MDM Cross-Env Change Detector"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.