When assigning or modifying permission sets, a license validation error appears if the user has not been assigned the proper Permission Set License (PSL). The system permissions for either View All Data (VAD) or Modify All Data (MAD) can cause similar errors after upgrading from CPQ 224 or CPQ 226 to a newer version. Permission sets granting access to Salesforce CPQ or Advanced Approvals Licensed Custom Objects (LCO) allows users to interact with each respective package. These two system permissions grant access to all objects, including CPQ and Advanced Approvals. Without a relevant license assigned, users may encounter validation errors similar to the ones triggered in the following scenarios:
"This permission set contains an object that requires a license. Before continuing, assign the user to the related permission set license."
Assigning a permission set that includes a user license such as Salesforce to a user or permission set group (when an assigned user also has the Permission Set License "Salesforce CPQ License". The additional user license conflicts with permissions to access CPQ licensed custom objects. To resolve this behavior, grant CPQ users a permission set that does not include a license.
Note - this error also occurs in the following scenarios:
To resolve the errors in the scenarios above, either the permissions to CPQ or AA licensed objects must be removed from the permission set or all assigned users must also be assigned the appropriate license. The steps below show how to create a custom permission set to grant permissions similar to View All Data (VAD) or Modify All Data (MAD) while excluding access to the licensed objects for CPQ or Advanced Approvals:
CPQ - Licensed Custom Objects
Advanced Approvals - Licensed Custom Objects
In an Org with CPQ/AA version 228 installed:
Verify ‘Object Settings’ to ensure the permissions are correctly marked. After revoking the system permissions View All Data or Modify All Data in CPQ/AA version 228, the object permissions remain intact for all objects except for Licensed Custom Objects. Unchecking the system permissions for VAD or MAD will only uncheck permissions to the licensed objects in the permission set; object permission checkboxes will still be checked for all non-licensed custom objects. For any object, when you uncheck Read access it will cascade and remove Create, Edit, Delete, View All Records, and Modify All Records access on that object.
NOTE: Muting permissions to LCOs in permission set groups in order to retain VAD or MAD access is not suggested. The VAD/MAD system permissions lose their ability to capture metadata changes when used in a permission set group. The permission set in the group containing either of these two system permissions need to be updated in order to capture the new metadata. Updates to the permission set can still result in validation errors if there are unlicensed users assigned to the permission set group.
000390789

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.