codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 3912 "Reten. Policy Telemetry Impl."

System Application · System.DataAdministration

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Codeunit 3909 "Retention Policy Log Impl." (calls, 6 links)Retention Policy Log Impl.Codeunit 8703 "Feature Telemetry" (calls, 2 links)Feature TelemetryCodeunit 3903 "Retention Policy Setup Impl." (calls)Retention Policy Setup Impl.Codeunit 3904 "Apply Retention Policy Impl." (calls)Apply Retention Policy Impl.

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.

System Application · System.DataAdministration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Permissions tabledata “Retention Policy Log Entry” = r

Event subscriptions

  • SendTelemetryOnAfterInsert subscribes to Table “Retention Policy Setup” OnAfterInsertEvent
  • SendTelemetryOnAfterModify subscribes to Table “Retention Policy Setup” OnAfterModifyEvent
  • SendTelemetryOnAfterDelete subscribes to Table “Retention Policy Setup” OnAfterDeleteEvent
  • OnModifyRetentionPolicySetup subscribes to Table “Retention Policy Setup” OnAfterModifyEvent
  • OnInsertRetentionPolicySetup subscribes to Table “Retention Policy Setup” OnAfterInsertEvent
  • OnDeleteRetentionPolicySetup subscribes to Table “Retention Policy Setup” OnAfterDeleteEvent
  • OnModifyRetentionPolicySetupLine subscribes to Table “Retention Policy Setup Line” OnAfterModifyEvent
  • OnInsertRetentionPolicySetupLine subscribes to Table “Retention Policy Setup Line” OnAfterInsertEvent
  • OnDeleteRetentionPolicySetupLine subscribes to Table “Retention Policy Setup Line” OnAfterDeleteEvent

Procedures

  • SendLogEntryToTelemetry(RetentionPolicyLogEntry: Record "Retention Policy Log Entry")
  • SendTelemetryOnRecordsDeleted(TableNo: Integer; TableName: Text; RecordCount: Integer; ManualRun: Boolean)
  • SendTelemetryOnInsertLogEntryInForegroundSessionStart(InitializationInProgress: Boolean; CurrenExecutionContext: ExecutionContext)
  • SendTelemetryOnInsertLogEntryInForegroundSessionEnd(InitializationInProgress: Boolean; CurrenExecutionContext: ExecutionContext)
  • SendTelemetryOnInsertLogEntryInBackgroundSessionStart(InitializationInProgress: Boolean; CurrenExecutionContext: ExecutionContext)
  • SendTelemetryOnInsertLogEntryInBackgroundSessionEnd(InitializationInProgress: Boolean; CurrenExecutionContext: ExecutionContext)
  • SendTelemetryOnInsertLogEntryInBackgroundSessionFailed(InitializationInProgress: Boolean; CurrenExecutionContext: ExecutionContext)

Plus 3 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: "Reten. Policy Telemetry Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources