BC Observatoryunofficial, made by waldo
codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 8400 "Record Set Management"

Base Application · System.IO

Open in Claude8400.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 1060 "Payment Service Setup" (calls, 4 links)Payment Service SetupCodeunit 10 "Type Helper" (calls, 2 links)Type HelperCodeunit 701 "Data Type Management" (calls)Data Type Management

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

Properties

Property Value
Permissions TableData “Record Set Definition” = rimd, TableData “Record Set Tree” = rimd

Procedures

  • SaveSetSingleTable(RecordsVariant: Variant): Integer
  • SaveSet(var TempRecordSetBuffer: Record "Record Set Buffer" temporary): Integer
  • GetSet(var TempRecordSetBuffer: Record "Record Set Buffer" temporary; SetID: Integer)
  • RenameRecord(RecRef: RecordRef; xRecRef: RecordRef)

Plus 7 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.

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 Set Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources