Deployment Error:

You may not turn off permission Access Activities 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 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:

1. Create a new repository in Git or use an existing one.
2. Clone the repository to your local machine.
3. Connect to Salesforce CPQ using the Salesforce CLI tool.
4. 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.

5. 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.

 Exception:   

System.QueryException: Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing.

Root Cause:

This exception is caused when the SOQL query is against on object with more than 200000 records and the query is not efficient. The query takes a longer time to execute and hence the exception.

Ex: Select Name,Email from Contact 

Ex: Select Name,Email from Contact where Status__c != NULL (Status__c is a custom non indexed field)

Resolution:

Option 1:

Make the query selective. Use Indexed fields when making the query selective, for example Id, CreatedDate, LastModifiedDate  etc are indexed.

Ex: Select Name,Email from Contact where LastModifiedDate  >=  LAST_N_DAYS:30

To find the indexed fields, use the object manager under setup

 Option 2:

If you need a custom field to be indexed, Salesforce support could add a custom index for you. Create a support case with Salesforce to get your custom index created. 

When the custom index is created, make your query selective using the custom indexed field.