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

Codeunit 9825 "Plan Configuration"

System Application · System.Azure.Identity

Across versions

  1. BC23-25present
  2. BC265 events removed
  3. BC27-30unchanged

Neighbourhood 11 connected objects and pages

Codeunit 9822 "Plan Configuration Impl." (calls, 12 links)Plan Configuration Impl.Table 9018 "Custom Permission Set In Plan" (calls, 4 links)Custom Permission Set In PlanCodeunit 9017 "Azure AD User Mgmt. Impl." (calls, 3 links)Azure AD User Mgmt. Impl.Codeunit 9018 "Azure AD Plan Impl." (calls, 3 links)Azure AD Plan Impl.Codeunit 9873 "BaseApp Security Group Impl." (calls, 2 links)BaseApp Security Group Impl.Codeunit 104030 "Upgrade Plan Permissions" (calls)Upgrade Plan PermissionsCodeunit 104061 "Upgrade User Groups" (calls)Upgrade User GroupsCodeunit 5684 "Create Contoso Permissions" (calls)Create Contoso PermissionsCodeunit 9032 "Upgrade Custom User Groups" (calls)Upgrade Custom User GroupsCodeunit 9087 "Microsoft 365 License Impl." (calls)Microsoft 365 License Impl.Page 1978 "MS 365 License Setup Wizard" (calls)MS 365 License Setup Wizard

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

Procedures

  • IsCustomized(PlanId: Guid): Boolean: Checks if a plan configuration was customized.
  • AddCustomPermissionSetToPlan(PlanId: Guid; RoleId: Code[20]; AppId: Guid; Scope: Option; Company: Text[30]): Adds a permission set to a plan.
  • RemoveCustomPermissionSetFromPlan(PlanId: Guid; RoleId: Code[20]; AppId: Guid; Scope: Option; Company: Text): Removes a permissions set from a plan.
  • AssignCustomPermissionsToUser(PlanId: Guid; UserSecurityId: Guid): Assigns all custom permission sets for a plan to a user.
  • RemoveCustomPermissionsFromUser(PlanId: Guid; UserSecurityId: Guid): Removes custom permission sets for a plan from a user. If the permission set is also associated with another plan, it is not deleted.
  • GetCustomPermissions(var PermissionSetInPlanBuffer: Record "Permission Set In Plan Buffer"): Gets the list of all custom permission sets for a plan.
  • AddDefaultPermissionSetToPlan(PlanId: Guid; RoleId: Code[20]; AppId: Guid; Scope: Option): Adds a permission set to a plan.
  • RemoveDefaultPermissionSetFromPlan(PlanId: Guid; RoleId: Code[20]; AppId: Guid; Scope: Option): Removes a permissions set from a plan.
  • AssignDefaultPermissionsToUser(PlanId: Guid; UserSecurityId: Guid; Company: Text[30]): Assigns all default permission sets for a plan to a user.
  • RemoveDefaultPermissionsFromUser(PlanId: Guid; UserSecurityId: Guid): Removes default permission sets for a plan from a user. If the permission set is also associated with another plan, it is not deleted.
  • GetDefaultPermissions(var PermissionSetInPlanBuffer: Record "Permission Set In Plan Buffer"): Gets the list of all default permission sets for a plan.
  • VerifyUserHasRequiredPermissionSet(RoleId: Code[20]; AppId: Guid; Scope: Option; Company: Text): Checks whether the current user has enough permissions to assign or de-assign a permission set from plan.

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 9822 “Plan Configuration Impl.” (12 calls: AddCustomPermissionSetToPlan → AddCustomPermissionSetToPlan, AddDefaultPermissionSetToPlan → AddDefaultPermissionSetToPlan, AssignCustomPermissionsToUser → AssignCustomPermissionsToUser, …)

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

Evidence 1 sources