Codeunit 5365 "CDS Int. Option Couple"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Integration Table Mapping |
Events published
OnBeforeRun(IntegrationTableMapping: Record "Integration Table Mapping"; var Handled: Boolean)(integration)OnBeforeSetMatchingFilter(var IntegrationRecordRef: RecordRef; var MatchingIntegrationRecordFieldRef: FieldRef; var LocalRecordRef: RecordRef; var MatchingLocalFieldRef: FieldRef; var SetMatchingFilterHandled: Boolean)(integration)
Procedures
PerformScheduledCoupling(var IntegrationTableMapping: Record "Integration Table Mapping")(internal)
Plus 9 local procedures.
Triggers
OnRun
Relations
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.” (6 calls:
CoupleRecords → CoupleOption,CoupleRecords → LogMatchBasedCouplingError,CoupleRecords → LogSynchError, …) - Codeunit 5340 “CRM Integration Table Synch.” (4 calls:
CoupleRecords → LoadCRMOption,OnRun → CloseConnection,OnRun → InitConnection, …) - Codeunit 5330 “CRM Integration Management” (3 calls:
CoupleRecords → CreateNewOptionsInCRM,SynchronizeCoupledRecords → EnqueueOptionSyncJobFromIntegrationTable,SynchronizeCoupledRecords → EnqueueOptionSyncJobToIntegrationTable) - Codeunit 5336 “Integration Record Synch.” (1 call:
CoupleRecords → SplitLocalTableFilter)
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: "CDS Int. Option Couple"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.