Codeunit 5333 "CRM Integration Telemetry"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Event subscriptions
- OnAfterInsertConnectionSetup subscribes to Table “CRM Connection Setup” OnAfterInsertEvent
- OnAfterModifyConnectionSetup subscribes to Table “CRM Connection Setup” OnAfterModifyEvent
- LogTelemetryOnAfterOpenCRMConnectionSetup subscribes to Page “CRM Connection Setup” OnOpenPageEvent
- LogTelemetryOnAfterOpenCRMConnectionSetupWizard subscribes to Page “CRM Connection Setup Wizard” OnOpenPageEvent
Procedures
LogTelemetryWhenConnectionEnabled()LogTelemetryWhenConnectionDisabled()
Plus 9 local procedures.
Triggers
OnRun
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 5330 “CRM Integration Management” (1 call:
GetEnabledConnectionTelemetryData → IsItemAvailabilityEnabled) - Codeunit 5344 “CRM Product Name” (1 call:
LogTelemetryWhenConnectionDisabled → SHORT)
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: "CRM Integration Telemetry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.