codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 3917 "Record Reference"

System Application · System.Reflection

Across versions

  1. BC23-30present

Neighbourhood 7 connected objects and pages

Codeunit 3920 "Reten. Pol. Record Ref. Impl." (event subscribers)Reten. Pol. Record Ref. Impl.Codeunit 8903 "Email Record Reference Impl." (event subscribers)Email Record Reference Impl.Codeunit 3915 "Reten. Pol. Filtering Impl." (calls, 3 links)Reten. Pol. Filtering Impl.Codeunit 3918 "Record Reference Impl." (calls, 2 links)Record Reference Impl.Codeunit 3904 "Apply Retention Policy Impl." (calls)Apply Retention Policy Impl.Codeunit 3916 "Reten. Pol. Delete. Impl." (calls)Reten. Pol. Delete. Impl.Codeunit 3994 "Reten. Pol. Doc. Arch. Fltrng." (calls)Reten. Pol. Doc. Arch. Fltrng.

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

Properties

Property Value
Access Public

Events published

  • OnInitialize(RecordRef: RecordRef; var RecordReference: Interface "Record Reference"; CallerModuleInfo: ModuleInfo; var IsInitialized: Boolean) (integration): Use this event to initialize the Record Reference interface with an implementation that has the required indirect permissions to read write to the table referenced by the RecordRef parameter.

Procedures

  • Initialize(RecordRef: RecordRef; var RecordReference: Interface "Record Reference"): Initializes the Record Reference interface. The method raises the OnInitialize event. If no subscriber initializes the interface, a default implementation is assigned.

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

Implemented 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: "Record Reference"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources