Symptom
- When inserting a document into another, the paragraph font of the parent document is lost if a custom field contains multi-line text.
- If the custom field contains single-line text, the paragraph font of the parent document is retained.
Environment
SAP CPQ
Reproducing the Issue
- Create a custom field of type long text.
- Reference the custom field in a document using the tag <<Q_TAG(<*CTX(Quote.CustomField(CustomField))*>)>>.
- Add the document (child document) to manage content documents.
- Create a template with a file containing <<Q_TAG_FILE(Document)>>.
- Ensure the child document uses one font type, and the parent document uses a different font type.
- Create a quote and add single-line text to the custom field.
- Generate the document.
- Verify that all paragraphs are styled with the font type defined in the parent document.
- Return to the quote and add multi-line text to the custom field.
- Generate the document again.
- Verify that the paragraph containing the custom field text now uses the font type of the child document instead of the parent document.
Cause
This is a bug.
Resolution
- A fix for this issue will be delivered in version 2602.
- As a workaround, ensure that the same font type is used in both the parent and child documents.
Keywords
Font, document, Custom field, inheritance, long text, CPQ , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Known Error
Product
SAP CPQ all versions
SAP Knowledge Base Article - Public