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

Codeunit 3998 "Retention Policy Scheduler"

Base Application · System.DataAdministration

Across versions

  1. BC23-25present
  2. BC261 procedures added
  3. BC27-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 3902 "Retention Policy Setup" (calls, 3 links)Retention Policy SetupCodeunit 3908 "Retention Policy Log" (calls, 2 links)Retention Policy Log

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 · System.DataAdministration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Permissions tabledata “Job Queue Category” = ri, tabledata “Job Queue Entry” = rim

Event subscriptions

  • CheckRetentionPolicyScheduleOnAfterInsert subscribes to Table “Retention Policy Setup” OnAfterInsertEvent
  • CheckRetentionPolicyScheduleOnAfterModify subscribes to Table “Retention Policy Setup” OnAfterModifyEvent
  • CheckRetentionPolicyScheduleOnAfterDelete subscribes to Table “Retention Policy Setup” OnAfterDeleteEvent

Procedures

6 local procedures, no public ones.

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 3902 “Retention Policy Setup” (3 calls: CheckRetentionPolicyScheduleOnAfterDelete → IsRetentionPolicyEnabled, CheckRetentionPolicyScheduleOnAfterInsert → IsRetentionPolicyEnabled, CheckRetentionPolicyScheduleOnAfterModify → IsRetentionPolicyEnabled)
  • Codeunit 3908 “Retention Policy Log” (2 calls: ScheduleRecurringRetentionPolicy → LogInfo, UnScheduleRecurringRetentionPolicy → LogInfo)

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: "Retention Policy Scheduler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources