Codeunit 7236 "Master Data Mgt. Tbl. Uncouple"

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

Properties

Events published

• OnBeforeRun(IntegrationTableMapping: Record "Integration Table Mapping"; var Handled: Boolean) (integration)

Procedures

5 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 5335 “Integration Table Mapping”

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 5335 “Integration Table Synch.” (5 calls: PerformScheduledUncoupling → BeginIntegrationUncoupleJob, PerformScheduledUncoupling → EndIntegrationSynchJob, UncoupleAllCoupledRecords → Uncouple, …)
• Codeunit 7233 “Master Data Management” (2 calls: UncoupleAllCoupledRecords → GetIntegrationRecordRef, UncoupleFilteredIntegrationRecords → OnSetSourceCompanyName)
• Codeunit 7231 “Integration Master Data Synch.” (1 call: UncoupleRecords → CreateMasterDataMgtCouplingClone)

Recent changes

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

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: "Master Data Mgt. Tbl. Uncouple"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.