Codeunit 5337 "CDS Int. Table Uncouple"

Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnBeforeRun(IntegrationTableMapping: Record "Integration Table Mapping"; var Handled: Boolean) (integration)

Procedures

6 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 5335 “Integration Table Mapping”

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.” (7 calls: PerformScheduledUncoupling → BeginIntegrationUncoupleJob, PerformScheduledUncoupling → EndIntegrationSynchJob, ResetStuckCompanyId → IncrementSynchJobCounters, …)
• Codeunit 5340 “CRM Integration Table Synch.” (4 calls: OnRun → CloseConnection, OnRun → InitConnection, OnRun → TestConnection, …)
• Codeunit 7201 “CDS Integration Impl.” (4 calls: ResetStuckCompanyId → FindCompanyIdField, ResetStuckCompanyId → HasCompanyIdField, ResetStuckCompanyId → ResetCompanyId, …)
• Codeunit 5336 “Integration Record Synch.” (1 call: ResetStuckCompanyId → SplitIntegrationTableFilter)

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. Table Uncouple"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.