BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 5397 "CDS Transformation Rule Mgt."

Base Application · Microsoft.Integration.Dataverse

Open in Claude5397.mdSource on GitHub

Across versions

  1. BC23-24present
  2. BC252 procedures changed, 1 procedures added
  3. BC26-27unchanged
  4. BC283 procedures removed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 5345 "Integration Rec. Synch. Invoke" (calls, 2 links)Integration Rec. Synch. InvokeCodeunit 5342 "CRM Synch. Helper" (calls)CRM Synch. Helper

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Event subscriptions

  • OnDeleteTransformationRule subscribes to Table “Transformation Rule” OnBeforeDeleteEvent

Procedures

  • ApplyTransformations(SourceRecordRef: RecordRef; var DestinationRecordRef: RecordRef; IntegrationTableMapping: Record "Integration Table Mapping") + BC25 Δ BC25 − BC28

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.

Called by

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

Evidence 1 sources