When executing the Post Install Scripts in Salesforce CPQ or when the CPQ package is installed or upgraded, the admin may receive a Post Install Script Failure email with the following message:
Please see the examples below to troubleshoot and resolve your post install script errors.
Follow the steps listed below to ensure that no permission errors occur when installing Salesforce CPQ or running Salesforce CPQ Post Install Scripts
If you're getting the error, 'line 77, column 1: Calculation authorization has expired and requires action by an administrator. Go to Installed Packages > Manage > Salesforce CPQ > Pricing and Calculation tab and reauthorize the new calculation service.' when trying to upgrade or install Salesforce CPQ, you need to reauthorize the calculation service.
Log in as an authorized user.
Reauthorize the calculation service through CPQ package settings.
Quote calculations should function and the post install script should successfully run after re-authorizing the calculation service. See this article on Best Practices when Authorizing the New Calculation Service for additional information.
When attempting to install a newer version of Salesforce CPQ, the install is failing with an error message: "(<object name>__c) Unmanaged custom object tab already exists, package upgrade cannot create another tab."
To allow the new version of the Salesforce CPQ package to install, an admin must delete or rename the existing tab that is conflicting with the new tab the package is attempting to create.
This can be done by navigating through Setup to the org Tabs settings (Setup > Create > Tabs). Find the tab corresponding to the object name in the error message. If the tab is an old managed package tab, it must be deleted. If it is a custom object tab with the same API name (without namespace), the object can be renamed or the tab can be deleted.
Once the tab has been edited or removed, you should attempt to re-install the new version of the package. It will no longer encounter the same tab error.
During post install script execution, custom validations and logic are not disabled in order to prevent invalid data. If you have records failing validation during the execution of Salesforce CPQ post-install scripts, you may see an error ‘FIELD_CUSTOM_VALIDATION_EXCEPTION: Custom validation error!’, if you see this error please consider the following solutions:
During post install script execution, you may see the error appear in your post install script failure 'Insert failed. First exception on row 25; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [Object Name]: [Object Name]'
This error may be thrown if you have Product Action records in the organization that have a Value Field (SBQQ__ValueField__c) defined with no Value Object(SBQQ__ValueObject__c) defined. Ensure that the Product Action's Value Field is NULL if there is no Value Object defined, and re-run the post-install scripts.
Upgrading to the most recent release will fail if the Quote's SBQQ__Opportunity__c master-detail field still exists. The error at the root of the failure states "common.exception.SfdcSqlException: ORA-20127: maximum depth of master-detail relationship exceeded."
In Salesforce CPQ Spring '19 a new object called QuoteLineConsumptionSchedule__c was introduced with a master detail relationship to QuoteLine__c. Quote Line's have a master detail relationship to Quotes and if the Quote's deprecated Opportunity master detail relationship field, SBQQ__Opportunity__c, still exists the master-detail relationship between Opportunity.Quote__c.QuoteLine__c.QuoteLineConsumptionSchedule__c exceeds the maximum depth allowed by Salesforce.
In Salesforce CPQ Summer '15 version 24.x, the SBQQ__Opportunity__c field was deprecated on Salesforce CPQ's Quote object. You should instead use the Quote's Opportunity lookup field, SBQQ__Opportunity2__c, to maintain the relationship between Quotes and Opportunities. Both SBQQ__Opportunity__c and SBQQ__Opportunity2__c should share the same values. Please see the following article for more information on how to Delete the Quote's Opportunity Master Detail Relationship Field
In some cases, installing Salesforce CPQ in an org can fail with this error:
"(ConsumptionSchedule.Category__c) Entity not available, Details: The Entity 'ConsumptionSchedule' is not found."
The error occurs because the org doesn’t have the CPQ license provisioned to it.
Production
Sandbox
Resolve the error by updating the licensing information in your Sandbox. Use one of these two methods to update your Sandbox org.
After refreshing your sandbox or matching production licenses, try installing Salesforce CPQ again.
You receive the following errors while installing Service Cloud for Salesforce CPQ
Resolution is to enable Entitlements in your org
NOTE: Rerun your post-install scripts if they initially fail. Post-install scripts only initialize package-managed fields that were installed. If your post-install scripts continue to fail, please get in contact with the customer support team.
000381759

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.