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

Codeunit 9057 "Plan Upgrade"

System Application · System.Azure.Identity

Across versions

  1. BC23-25present
  2. BC261 procedures added
  3. BC27-30unchanged

Neighbourhood 4 connected objects and pages

Codeunit 9027 "Plan Ids" (calls, 24 links)Plan IdsCodeunit 9999 "Upgrade Tag" (calls, 22 links)Upgrade TagCodeunit 9058 "Plan Upgrade Tag" (calls, 11 links)Plan Upgrade TagCodeunit 9822 "Plan Configuration Impl." (calls)Plan Configuration Impl.

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

Properties

Property Value
Subtype Upgrade
Permissions tabledata Plan = rimd

Procedures

14 local procedures, no public ones.

Triggers

OnUpgradePerDatabase

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.

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

Evidence 1 sources