codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 104030 "Upgrade Plan Permissions"

Base Application · Microsoft.Upgrade

Across versions

  1. BC23-24present
  2. BC251 procedures added
  3. BC26-30unchanged

Neighbourhood 8 connected objects and pages

Codeunit 9027 "Plan Ids" (calls, 41 links)Plan IdsCodeunit 9999 "Upgrade Tag" (calls, 22 links)Upgrade TagCodeunit 9998 "Upgrade Tag Definitions" (calls, 11 links)Upgrade Tag DefinitionsCodeunit 104061 "Upgrade User Groups" (calls, 4 links)Upgrade User GroupsCodeunit 457 "Environment Information" (calls, 4 links)Environment InformationCodeunit 6723 "Server Setting" (calls, 3 links)Server SettingCodeunit 6060 "Hybrid Deployment" (calls)Hybrid DeploymentCodeunit 9825 "Plan Configuration" (calls)Plan Configuration

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

Properties

Property Value
Subtype Upgrade
Permissions TableData “User Group Plan” = rimd

Procedures

  • RunUpgrade() (internal)
  • ReplaceUserGroupPermissionSets(UserGroupCode: Code[20]; NewComposedPermissionSet: Code[20]; Scope: Option System,Tenant) (internal)
  • AddUserGroupMember(UserGroupCode: Code[20]; UserSecurityID: Guid; SelectedCompany: Text[30]) (internal)

Plus 38 local procedures.

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” (41 calls: AddAutomateActionUserGroupToExistingPlans → GetAccountantHubPlanId, AddAutomateActionUserGroupToExistingPlans → GetBasicFinancialsISVPlanId, AddAutomateActionUserGroupToExistingPlans → GetBasicPlanId, …)
  • Codeunit 9999 “Upgrade Tag” (22 calls: AddFeatureDataUpdatePermissions → HasUpgradeTag, AddFeatureDataUpdatePermissions → SetUpgradeTag, CreateBCAdminPermissions → HasUpgradeTag, …)
  • Codeunit 9998 “Upgrade Tag Definitions” (11 calls: AddFeatureDataUpdatePermissions → GetAddFeatureDataUpdatePermissionsUpgradeTag, CreateBCAdminPermissions → GetBCUserGroupUpgradeTag, CreateD365EssentialAttachPermissions → GetEssentialAttachUserGroupUpgradeTag, …)
  • Codeunit 457 “Environment Information” (4 calls: InsertPermission → IsSaaS, SetAutomateAccessControl → IsSaaS, SetAutomateActionPermissions → IsSaaS, …)
  • Codeunit 6723 “Server Setting” (3 calls: AddPermissionSetToUser → GetUsePermissionSetsFromExtensions, InsertPermission → GetUsePermissionSetsFromExtensions, TryInsertPermissionSet → GetUsePermissionSetsFromExtensions)
  • Codeunit 104061 “Upgrade User Groups” (2 calls: RunUserGroupUpgrade → IsUserGroupObsoleteStateRemoved, SetAutomateActionPermissions → IsUserGroupObsoleteStateRemoved)
  • Codeunit 6060 “Hybrid Deployment” (1 call: RunUpgrade → VerifyCanStartUpgrade)
  • Codeunit 9825 “Plan Configuration” (1 call: AddPermissionSetToPlan → AddDefaultPermissionSetToPlan)

Called by

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

Evidence 1 sources