Skip to main content

Removing rows with the Deleterow tag

Using the Deleterow tag in a report template provides an easy way to remove a row that you do not need included in your report output, but is required to be included in your template to make it function correctly.

When you create native Excel tables in your report template, your table must include a blank row at the bottom. This ensures that the Qlik add-in for Microsoft Excel propagates any native Excel formulas on every row of the table. If you do not include a blank row and you add Excel calculated columns or row totals, the formula will only be applied to the row where you defined it, not the entire table.

Insert a <deleterow> tag in this blank row if you do not want a blank row to appear in the generated report.

If your report template has blank rows that you do not want to appear in the generated report, use the <deleterow> tag. This is often done to remove the gap between table data and totals. Deleterow tags are not mandatory. If you do not add one to the empty row, you will simply have a table with a blank row at the end.

You can also add <deleterow> tags below standard tabular data added from a Qlik Sense chart, or in any row in the template file. This performs the same function, removing the row the tag is inserted on.

Example

Let's say you have created a native Excel table, and want the last, blank row (which is required to generate the proper report output) to be removed in the generated report. Add the <deleterow> tag according to the image below.

Required use of <deleterow> tag to remove last row in Excel table

Deleterow tag inserted at the bottom of a native Excel table

In the generated report, the table will appear like the image below.

Generated report output after using <deleterow> tag in template

Output generated from use of Deleterow at bottom of native Excel table. The bottom, blank row is removed from the output

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!