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

Codeunit 9621 "DesignerPageId"

Base Application · System.Tooling

Open in Claude9621.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Page 9620 "Page Fields" (calls)Page FieldsPage 9621 "Add Page Fields" (calls)Add Page Fields

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

Properties

Property Value
SingleInstance true

Procedures

  • GetPageId(): Integer
  • SetPageId(PageId: Integer): Boolean

Triggers

OnRun

Called by

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.

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

Evidence 1 sources