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

Codeunit 9058 "Plan Upgrade Tag"

System Application · System.Azure.Identity

Across versions

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

Neighbourhood 2 connected objects and pages

Codeunit 9057 "Plan Upgrade" (calls, 11 links)Plan UpgradeCodeunit 9056 "Plan Installer" (calls)Plan Installer

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
Access Public

Event subscriptions

  • RegisterPerDatabaseTags subscribes to Codeunit “Upgrade Tag” OnGetPerDatabaseUpgradeTags

Procedures

  • GetAddDeviceISVEmbUpgradeTag(): Code[250]: Returns the device upgrade tag.
  • GetRenamePlansUpgradeTag(): Code[250] (internal): Returns the rename plans upgrade tag.
  • GetRenameTeamMemberPlanUpgradeTag(): Code[250] (internal): Returns the rename team member plan upgrade tag.
  • GetRenameDevicePlanUpgradeTag(): Code[250] (internal): Returns the rename device plan upgrade tag.
  • GetPremiumPartnerSandboxUpgradeTag(): Code[250] (internal): Returns the Premium Partner Sandbox upgrade tag.
  • GetMicrosoft365UpgradeTag(): Code[250] (internal): Returns the Microsoft 365 upgrade tag.
  • GetEssentialAttachUpgradeTag(): Code[250] (internal): Returns the Essential Attach upgrade tag.
  • GetMD365AdminUpgradeTag(): Code[250] (internal): Returns the Dynamics 365 Administrator upgrade tag.
  • GetDelegatedD365AdminUpgradeTag(): Code[250] + BC26 (internal): Returns the Delegated Dynamics 365 Administrator upgrade tag.
  • GetBCAdminUpgradeTag(): Code[250] (internal): Returns the BC Administrator upgrade tag.
  • GetPlanfigurationsUpgradeTag(): Code[250] (internal)

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

Evidence 1 sources