BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 5523 "API Fix Document Shortcut Dim."

Base Application · Microsoft.API.Upgrade

Open in Claude5523.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 9994 "API Data Upgrade" (calls, 6 links)API Data Upgrade

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

Procedures

  • UpgradeSalesInvoiceShortcutDimension()
  • UpgradePurchInvoiceShortcutDimension()
  • UpgradePurchaseOrderShortcutDimension()
  • UpgradeSalesOrderShortcutDimension()
  • UpgradeSalesQuoteShortcutDimension()
  • UpgradeSalesCrMemoShortcutDimension()

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.

  • Codeunit 9994 “API Data Upgrade” (6 calls: UpgradePurchaseOrderShortcutDimension → UpgradePurchaseOrderShortcutDimension, UpgradePurchInvoiceShortcutDimension → UpgradePurchInvoiceShortcutDimension, UpgradeSalesCrMemoShortcutDimension → UpgradeSalesCrMemoShortcutDimension, …)

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: "API Fix Document Shortcut Dim."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources