Symptom
- For Quote 1.0 engine, in the new 2505 release, the language selection does not function as expected when generating a document.
Environment
SAP Sales Cloud CPQ
Reproducing the Issue
- Open a sample quote.
- Click on 'Generate Document'.
- Select a non-English language
- Click on 'Generate'.
- Download the generated document.
- The generated document appears in English, regardless of the selected language.
Cause
- The issue occurs when you are using the tag
<<Q_CUSTOM_FIELD(Customer's Language)>>
within the template. - On the old pages, the custom field Customer's Language was used to store the selected translation language on the card.
- The new design is based on the quote 2.0 logic and therefore does not rely on this custom field.
- This means that the Customer's Language field will not be updated when the user selects a language for document generation.
- As a result, the tag
<<Q_CUSTOM_FIELD(Customer's Language)>>
will not return the expected value.
Resolution
- A code correction has been created to ensure that this custom field is considered on the new pages as well.
- The code correction will be deployed on Saturday 31May2025 (tentative).
- Until Saturday, as a workaround, the tag
<<Q_TAG(<*CTX( Dictionary.Current.Id )*>)>>
can be used instead<<Q_CUSTOM_FIELD(Customer's Language)>>
. - This tag returns the ID of the currently selected dictionary at the moment of generation — which is the same value that would otherwise be written to the custom field 'Customer's Language'.
- The final option would be to revert the client back to the old document generation pages. This fallback can only be considered if customer have a significant number of templates where the tag replacement is not feasible, and if the issue is critically blocking their business process.
See Also
3487591 - Known Issues in SAP CPQ
Keywords
Quote 1.0, SAP CPQ, document generation, docgen, language selection, custom field, dictionary ID, quote 2.0 logic. , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Problem
Product
SAP CPQ all versions