Codeunit 9057 "Plan Upgrade"
System Application · System.Azure.Identity
Across versions
- BC23-25present
- BC261 procedures added
- BC27-30unchanged
Neighbourhood 4 connected objects and pages
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.
- Codeunit 9027 “Plan Ids” (24 calls:
AddBCAdmin → GetBCAdminPlanId,AddBCAdmin → GetDelegatedBCAdminPlanId,AddD365Admin → GetD365AdminPlanId, …) - Codeunit 9999 “Upgrade Tag” (22 calls:
AddBCAdmin → HasUpgradeTag,AddBCAdmin → SetUpgradeTag,AddD365Admin → HasUpgradeTag, …) - Codeunit 9058 “Plan Upgrade Tag” (11 calls:
AddBCAdmin → GetBCAdminUpgradeTag,AddD365Admin → GetMD365AdminUpgradeTag,AddDefaultPlanConfigurations → GetPlanfigurationsUpgradeTag, …) - Codeunit 9822 “Plan Configuration Impl.” (1 call:
AddDefaultPlanConfigurations → CreateDefaultPlanConfigurations)
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.