Codeunit 7246 "MDM Source Capabilities"
MasterDataManagement · Microsoft.Integration.MDM
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
MasterDataManagement · Microsoft.Integration.MDM · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| SingleInstance | true |
Procedures
EnsureSupported(Transport: Interface "IMDM Source Transport"; Feature: Text)IsSupported(Transport: Interface "IMDM Source Transport"; Feature: Text): BooleanContractVersionNo(Transport: Interface "IMDM Source Transport"): IntegerReset()
Plus 4 local procedures.
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” (1 call:
RaiseCapabilitiesParseError → GetTelemetryCategory)
Called by
- Codeunit 7249 “MDM Cross-Env Data Source” (6 calls:
FetchBySystemIds → EnsureSupported,GetModifiedBatch → EnsureSupported,GetSourceRecordsByFilter → EnsureSupported, …) - Codeunit 7245 “MDM Cross-Env Change Detector” (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 Source Capabilities"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.