N Printing Pixel Perfect blank rows in table

[Fawad]

Hi,

I'm currently having an issue with a pixel perfect report generating blank rows when it loops through my business units.

There are no blank/null business units in my Qlik Sense report, however when it creates the report it has blank rows. 

I've tried writing some c# code to remove these blank rows where the length of column 1 equals 0 or is null using dev express library.

I can remove the row entirely but can't remove only the blank rows.

https://docs.devexpress.com/XtraReports/DevExpress.XtraReports.UI.XRGroupSortingSummary.IgnoreNullVa...

I've also contacted Qlik directly and was referred back to the link above. Has anyone had this issue before??

[Ruggero_Piccoli]

Hi,

Could you please post some screenshots of the template and the generated report with blank rows? 

If you created the PixelPerfect table by using levels and you inserted the Qlik Sense straight table in the level you should see the same rows you see in Sense.

If you are nesting levels, remember that in PixelPerfect you must create the hierarchy  in the Levels node.

Best Regards,

Ruggero

[Fawad]

Hi,

Thanks for your reply.

I've created a hierarchy in the levels node but its still creating blank rows.

Attached is a screenshot of the template editor and the output of the report.

Thanks

[Ruggero_Piccoli]

Hi,

As documented in https://help.qlik.com/en-US/nprinting/November2019/Content/NPrinting/PixelPerfectReports/Add-Totals-..., when you want to create a native table in a PixelPerfect template you must add the source straight table in the Levels node at the correct nesting position.

In PixelPerfect templates the Tables node is used only to add the tables used as data sources for native charts.

From the screenshot it seems that you are adding fields form the Tables node inside the KeyJobDetail band because the fields visible in that band are not available under the KeyJobRole_Level_1 in the Levels node. You need to remove the source table from the Tables node and add it under KeyJobRole_Level_1 in the Levels node. Then add the fields in the template again.

Best Regards,

Ruggero