Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

NPrinting shows only one row of table, need all

Dear Community,

inside a pixel perfect report i add a report header and a detail band.

After that i added a table object and inside the table header i defined the headers of the table and inside the detail band the columns that have a data binding.

2.png

When i preview the result, i see only one (the first) row and NOT all the rows of the table.

What did i wrong?

Please help

13 Replies
Anonymous
Not applicable
Author

No one can help?

this is really important as i get only the first row of all tables actually.

I need all rows of an table!

Not applicable
Author

The template should look something like the attached image.

If you send a screen shot with the entire Field list expanded as well as another screen shot of the template grid (the right hand side where you drag and drop fields and create headers...) that would help

Anonymous
Not applicable
Author

Hi Aran,

it looks quite similar, see:1.png

2.png

Not applicable
Author

Try adding your charts as levels and not as tables.

That should fix the issue.

The levels node is at the top, above "Images".

Anonymous
Not applicable
Author

If using levels and just drag and drop everything inside the sheet the preview comes never back.

If Using a levels field inside a table i get following error:

3.png

Not applicable
Author

try following this tutorial:

How to Create a Simple PixelPerfect Report

Anonymous
Not applicable
Author

Hi Aran, we are already following this tutorial. Every time we use levels we get the "preview request failed with message" error (see my last message). I opened a support ticket @ qlik.

berryandcherry6
Creator III
Creator III

Hi,

Even i am facing the same issue, i am getting only first row in table.

how did you solve that issue?

Regards

Anonymous
Not applicable
Author

Hi Supriya,

after consultation with Qlik, it seems that is an offical bug .

I do not have any information, when it will be solved.