Symptom
- Standalone
[CONDITION]and[CONDITION_END]tags defined in an Excel document generation template are not evaluated during document generation. - The generated Excel document displays the condition tags as plain text and the expected filtering or removal of rows does not occur.
Environment
SAP Sales Cloud CPQ
Reproducing the Issue
- Navigate to a quote.
- Click on "Generate Documents".
- Select the relevant excel template to generate the document.
- Download the generated document.
- Observe that the condition is not evaluated in the generated Excel file and the CONDITION tags appear in the output instead of filtering the rows.
Cause
- Standalone condition blocks defined using
[CONDITION]and[CONDITION_END]tags are not supported in Excel document generation templates. - Excel templates support only tag-level conditions, where the condition is applied directly on the tag.
Resolution
Modify the Excel document generation template to apply the condition directly at the tag level instead of using standalone [CONDITION] and [CONDITION_END] blocks.
For example:
<<QUOTE_TABLE_COLUMN(<column_name>),<value>=d>>
In this example, if the condition is met, the value returned by the tag is deleted.
Excel templates support the following condition actions:
-
d – Deletes the value returned by the tag when the condition is met.
-
DR – Deletes the entire row when the value is displayed inside a table.
See Also
Keywords
quote table condition, excel template, condition tags, standalone condition, tag-level condition, document generation, rows not filtered, Sales Cloud CPQ, CONDITION , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Problem
SAP Knowledge Base Article - Public