CPQ errors on attempt to generate or preview Quote Documents

Quote Template Detail

Check all color fields on the Quote Template Detail to make sure their values are a valid Hexadecimal color code. Using Data Loader to migrate from Sandbox to Production can cause a HEX value of "000000" to be saved as "0". Also check all color fields in all template sections by clicking on the Section Name in the Sections related list on the Quote Template record. If this was caused by a data migration using a spreadsheet and Data Loader, you may be able to prevent this by ensuring that your cells in the spreadsheet are formatted as text and not as numbers. 

1. Determine Which Section is Causing the Error

1. Clone the Quote Template using the Clone with Related button (may have to be added to the layout). Always work with a copy to maintain your original as a backup.
2. From your cloned template, remove one section at a time until the document renders. 
3. The last section removed is causing an error. There may be other sections with errors that were removed previously, but this has to be done one at a time.
4. Add the last section removed to a brand new Quote Template as the only section. Use this for testing.
5. The error may be caused by the template's Header and/or Footer content. If the error(s) persist after removing all Sections, try removing the Quote Template lookup field values for SBQQ__HeaderContent__c and SBQQ__FooterContent__c.

2. Fixing Common Template Section Errors

1. If the problem section is of type Line Items, recreate it from scratch making sure all custom field API names are spelled correctly.
2. If the problem section is of type HTML, go to Template Content and click on the name of the cloned Template Content record.
3. Click Edit to open the content editor.
4. Delete Tables, Rows, or Columns one at time, save, and test by previewing the template to try to identify which section of the code is causing the error. 
5. To recreate your custom template section, use the Template Content editor tools. Don't paste from a formatted document source like MS Office. Not all HTML tags and formatting are supported. 
6. You may need to log a support case so we can further assist in troubleshooting.

3. A Bad Request Error on Preview/Generate Document can be caused by the following

1. Unsupported styling tags used in Template Content.
2. Template Section is tied to Template Content of type Line Items, with no available Line Columns (all Line Columns are tied to other sections)
3. Session Settings have High Assurance set at Profile or Org level.
4. Incorrect field or object API Name is referenced in the template.
5. An & character included in the text is not formatting correctly in the wysiwyg. Click Edit and then 'Save' on the Template Content to re-format it correctly.
6. An improper reference to an image. The reference to the image needs to include the same URL namespace as the acting Org. For example, an image with a reference to a Production URL will cause the Bad Request error when Previewing/Generating in a lower environment like a QA Sandbox. 
7. Confirm the record Id for the image referenced in the URL above is correct for the acting Org.

4. Failed to Load PDF Document

This error often occurs due to changes in the row and column layout of the HTML table that holds the custom Template Content.
If the issue is reproducible in more than one browser, there is one permission that needs to be disabled which resolve the issue:

1. Navigate to Setup | Security | Session Settings
2. Disable the setting 'Lock sessions to the IP address from which they originated'

Workaround

1. Clone the custom Template Section used in the Quote Template
2. Replace the referenced Template Content in each respective Quote Template Section with the Cloned TEST Template Content from Step 1.
3. Delete Tables, Rows, or Columns one at time in each Template Content Section. After each deletion, Preview the Document to try to identify which section of the code is flawed and causing the error.
4. Remove non-working HTML or log a Salesforce CPQ & Billing Support Case so we can assist in troubleshooting the source code and fixing the section.

5. Failed to Load PDF Document error due to unintentional field value changes

Workaround

For some users, migrating from Sandbox to Production using the Data Loader cause field values with more than one 0 to be truncated to a single zero. This is most common for color field values written in color hexadecimal, i.e. 000000 for black:

This is an Excel and Data Loader issue unrelated to SteelBrick functionality. However, you can work around this by ensuring your cells in Excel are formatted as text and not as numbers. You can also manually change any already-truncated numbers on the Quote Template.
 

An error occurred rendering the document. Please check the Quote Template for invalid HTML markup

This error often occurs due to copy/paste of Word or other documents containing hidden HTML tags in HTML Template Content.

Workaround

1. Paste the content into a text editor such as Notepad, save the document, then copy/paste from the text editor into the HTML Template Content.
2. Review the raw HTML source code rather than the WYSIWYG text editor. Remove content line by line. After each deletion, preview the document until the offending line is found that causes the error.

6. Preview Documents

If you see the error 'You do not have insert access on object Quote Document. Please contact your administrator" while previewing Quote Documents, follow the steps below to troubleshoot the issue:  

1. Ensure that the user permissions include "Quote Documents - Create"
2. This can be added either on a Profile or Permission Set

7. Additional troubleshooting

If you're still experiencing problems rendering the document, review these items:

1. Check if you're linking URLs or images from a sandbox and confirm if that sandbox was refreshed. If the sandbox was refreshed, this can change the URL/Pod it's on. 
2. Check if an ampersand (&) exists in an image URL in your Template Content. Ampersands can cause errors because the markup field attempts to correct them. Update the "&" to "&" or go to your Template Content and click edit. Next view the source, and then save. This corrects the image URL with the proper markup to generate. 
3. Make sure the photo is shared externally. Users see this error if the photo in the linked URL or in the HTML, referenced in the Company Logo field, isn't shared externally. 
4. If you are seeing the Attempt to de-reference a null object error, it usually means that one or more related Quote Lines price fields (e.g. SBQQ__NetPrice__c, SBQQ__NetTotal__c, SBQQ__UnitCost__c, etc) are null but require a value. To resolve this, ensure CPQ price fields do not have null values.