Codeunit 7242 "MDM Privacy Notice"
MasterDataManagement · Microsoft.Integration.MDM
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
MasterDataManagement · Microsoft.Integration.MDM · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Event subscriptions
- RegisterPrivacyNotice subscribes to Codeunit “Privacy Notice” OnRegisterPrivacyNotices
Procedures
GetPrivacyNoticeId(): Code[50]IsApproved(): BooleanConfirmApproval(): BooleanCheckApproved()
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 1563 “Privacy Notice” (2 calls:
ConfirmApproval → ConfirmPrivacyNoticeApproval,IsApproved → GetPrivacyNoticeApprovalState)
Called by
- Page 7232 “MDM Connection Details” (2 calls:
NextStep → ConfirmApproval,NextStep → IsApproved) - Codeunit 7241 “MDM Cross-Env Source API” (1 call:
IsSourceConsented → IsApproved) - Codeunit 7247 “MDM Http Source Transport” (1 call:
InvokeAction → CheckApproved)
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 Privacy Notice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.