codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 4470 "Record Link Impl."

System Application · System.Utilities

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 447 "Record Link Management" (calls, 6 links)Record Link ManagementCodeunit 27 "Confirm Management" (calls)Confirm ManagementCodeunit 459 "Remove Orphaned Record Links" (calls)Remove Orphaned Record Links

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

Properties

Property Value
Access Internal
SingleInstance true
Permissions tabledata “Record Link” = rimd

Procedures

  • WriteNote(var RecordLink: Record "Record Link"; Note: Text)
  • ReadNote(RecordLink: Record "Record Link"): Text

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

Evidence 1 sources