Deployment Error:
- You may not turn off permission Lightning Console User for this License Type
Resolution:
This is a default permission and cannot be set to FALSE. Set it to TRUE in the xml file and deploy.
Deployment Error:
You may not turn off permission View Help Link for this License Type
Resolution:
This is a default permission and cannot be set to FALSE. Set it to TRUE on the XML file and deploy
Deployment Error:
You may not turn off permission View Help Link for this License Type
Resolution:
This is a default permission and cannot be set to FALSE. Set it to TRUE in the XML file and deploy
Deployment Error:
"You may not turn off permission Enable Chatter for this License Type"
Resolution:
This is a default permission and cannot be set to FALSE. Set it to TRUE on the XML file and deploy.
Select count(Id),Owner.Name from Case where IsClosed = false and Owner.isActive = true and OwnerID IN (SELECT Id FROM Group WHERE Type = 'Queue') GROUP BY Owner.Name
Salesforce CPQ configuration data can be version controlled using a source control system like Git. Here are the steps to version control Salesforce CPQ config data:
- Create a new repository in Git or use an existing one.
- Clone the repository to your local machine.
- Connect to Salesforce CPQ using the Salesforce CLI tool.
- Use the Salesforce CLI to retrieve the CPQ configuration data in XML format. You can do this by running the following command:
sfdx force:source:retrieve -m CustomObject:ProductRule -u your-org-alias
Replace CustomObject:ProductRule with the metadata type you want to retrieve.
- Commit the retrieved metadata files to your Git repository.
By version controlling the Salesforce CPQ configuration data, you can easily track changes to the CPQ configuration, roll back changes if necessary, and collaborate with other team members on the same project.
Note that version controlling CPQ configuration data requires careful planning and collaboration among the team members to avoid conflicts and ensure smooth synchronization of changes.
