Codeunit 489 "IC Partner Change Monitor"
Base Application · Microsoft.Intercompany.DataExchange
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Intercompany.DataExchange · BC23-30 · source at ea08af5e · facts from BC29
Event subscriptions
- CheckPermissionsBeforeInsert subscribes to Table “IC Partner” OnBeforeInsertEvent
- CheckPermissionsOnBeforeModifyEvent subscribes to Table “IC Partner” OnBeforeModifyEvent
- CheckPermissionsOnBeforeDeleteEvent subscribes to Table “IC Partner” OnBeforeDeleteEvent
- CheckPermissionsOnBeforeRenameEvent subscribes to Table “IC Partner” OnBeforeRenameEvent
Procedures
CheckHasPermissionsToChangeSensitiveFields()(internal)RegisterActivity(var ICPartner: Record "IC Partner"; Context: Text[30]; ActivityDescription: Text; ActivityMessage: Text)(internal)
Plus 1 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 152 “User Permissions” (2 calls:
CheckHasPermissionsToChangeSensitiveFields → HasUserPermissionSetAssigned,CheckHasPermissionsToChangeSensitiveFields → IsSuper) - Codeunit 8703 “Feature Telemetry” (2 calls:
RegisterActivity → LogUptake,RegisterActivity → LogUsage) - Codeunit 428 “IC Mapping” (1 call:
RegisterActivity → GetFeatureTelemetryName) - Codeunit 457 “Environment Information” (1 call:
RegisterActivity → IsSaaSInfrastructure)
Called by
- Page 561 “CrossIntercomp. Partner Setup” (2 calls:
OnOpenPage → CheckHasPermissionsToChangeSensitiveFields,SaveConfigurationToTemporaryPartner → CheckHasPermissionsToChangeSensitiveFields) - Page 565 “CrossIntercompany Modify Setup” (2 calls:
PopulatePartnerSensibleDetails → CheckHasPermissionsToChangeSensitiveFields,SaveConfigurationToTemporaryPartner → CheckHasPermissionsToChangeSensitiveFields)
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: "IC Partner Change Monitor"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.