Loading

Salesforce CPQ and Advanced Approvals profile Best Practices to prepare for the Winter '21 release

Udgivelsesdato: Jul 2, 2025
Beskrivelse
Beginning in the Winter '21 releases for CPQ and Advanced Approvals (AA), profiles are no longer able to grant access to any Salesforce Licensed Custom Objects (LCO). To interact with CPQ or AA related objects, users are required to have Permission Set Licenses (PSL) assigned. Validation error messages will appear when editing permissions in profiles or permission sets in 228 if any user belonging to the group does not have an appropriate license. Existing profiles granting access to CPQ or AA objects may be in an invalid state post upgrade if they grant permissions to these objects. The permissions in these profiles will still be active, but admins will see errors when trying to save any edits to the profile. The Managed Package License (MPL) will transition to a site license post-upgrade to 228. 
 
NOTE: Removal of Managed Package License assignments, before or after upgrading, can result in users being unable to see CPQ related objects. If you have upgraded to CPQ 228 (Winter '21) and users are unable to see these objects, re-assign MPLs to the affected users. Log a case with support if there are additional concerns.

Permissions to the following Licensed Custom Objects (LCO) and their related dependent objects cannot be granted to users via profile:
 

CPQ Licensed Custom Objects - 6 (Related Dependent Objects - 18)

  1. Price Rule 
    1. (Price Action, Price Condition, Lookup Query)
  2. Pricing Guidance 
    1. (Pricing Guidance Tier)
  3. Product Rule 
    1. (Configuration Rule, Error Condition, Product Action)
  4. Quote 
    1. (Quote Document, Quote Line, Quote Line Group, Quote Line Pricing Guidance, Quote Line Consumption Schedule, Quote Line Consumption Rate)
  5. Quote Template 
    1. (Line Column, Template Section)
  6. Subscription
    1. (Subscribed Asset, Subscription Consumption Schedule, Subscription Consumption Rate)

Advanced Approvals Licensed Custom Objects - 2 (Related Dependent Objects - 2)

  1. Approval
    1. (Approval Snapshot)
  2. Approval Rule
    1. (Approval Condition)
NOTE: 
  • Dependent objects can include any custom object that uses a CPQ or AA licensed object in a Master-Detail relationship. Permissions granted to a custom object may also require the user to have a permission set license, after the upgrade to CPQ 228 or AA 228, because of the relationship's dependence on a licensed object.
  • The DocuSign Recipient object defines Quote Template as the master in their master-detail relationship. As such, Orgs that are using DocuSign may need to remove permissions to the DocuSign Recipient object if the person is not a designated CPQ user with a related license. Otherwise, the user will be required to have a CPQ Permission Set License assigned.

Profile errors may occur in the following scenario:
  1. Existing profile grants permissions to the LCOs listed above
  2. Users of said profile do not have a required license assigned
  3. Editing and saving the profile changes will return the following:
  • ERROR: [PERMISSION NAME] on [OBJECT NAME] can't be granted. Grant the permission using a permission set with the required license or use a permission set not associated with a specific license.
 

ADDITIONAL EXAMPLES:
  • Read on Quote can't be granted. Grant the permission using a permission set with the required license or use a permission set not associated with a specific license.
  • Read on Approval can't be granted. Grant the permission using a permission set with the required license or use a permission set not associated with a specific license.
 
NOTE: The license attached to profiles such as Community users can affect the visibility of CPQ and AA objects when making profile edits beginning in CPQ 228. Certain partner community user profiles may be in a non-compliant state post upgrade to 228 and are unable to view or edit those permissions because of the User License that accompanies the profile. To remove the object permissions from these profiles, use API calls to make the necessary edits. 
Løsning

The best practice to address this change is to remove any AA or CPQ permissions to licensed custom objects, including related dependent objects, from the profile. Instead, assign permissions for these objects in a permission set and assign it to users. To return the profiles to a valid state in the 228 release, profiles must be edited to remove permissions to any LCO or related objects. 

 

Profile Editing Tip:

When utilizing the Enhanced Profile User Interface, profile edits are limited to a single object at a time. To update multiple object permissions at once, administrators can disable this feature which changes the UI layout for profiles. Here is the path to disable this feature:

Setup > User Management Settings > Disable “Enhanced Profile User Interface”

Refresh the profile page to see the legacy user interface layout. Editing the profile now allows the removal of multiple object permissions at one time.

For details on permission set best practices and potential errors relating to user licenses in CPQ or AA version 228 and beyond can be found in this article.

Vidensartikelnummer

000389406

 
Indlæser
Salesforce Help | Article