Codeunit 5347 "Integration Rec. Delete Invoke"
Base Application · Microsoft.Integration.SyncEngine
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Integration.SyncEngine · BC23-30 · source at ea08af5e · facts from BC29
Events published
OnBeforeDeleteRecord(IntegrationTableMapping: Record "Integration Table Mapping"; var DestinationRecordRef: RecordRef)(integration)OnAfterDeleteRecord(IntegrationTableMapping: Record "Integration Table Mapping"; var DestinationRecordRef: RecordRef)(integration)
Procedures
SetContext(IntegrationTableMapping: Record "Integration Table Mapping"; DestinationRecordRef: RecordRef; SynchAction: Option; JobId: Guid)GetContext(var IntegrationTableMapping: Record "Integration Table Mapping"; var DestinationRecordRef: RecordRef; var SynchAction: Option)
Plus 3 local procedures.
Triggers
OnRun
Called by
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.” (3 calls:
Delete → (object),Delete → GetContext,Delete → SetContext)
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: "Integration Rec. Delete Invoke"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.