Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am using nprinting version September 2017, Qlik Sense version June 2017.
My test data has dimension Provider, two values A and B. In the nprinting report, cycle is enabled on field Provider. The zip file created has two files, Proms1ReportA.xslx and Proms1ReportB.xlsx. However the content of the files is identical - both have all records for both providers.
Is an extra step required to filter the data in each report to the cycle field?
Steps used to create nprinting report:
1. Created nprinting app Proms1.
2. Created connection Proms1Connection. Cache generated.
3. Created report, type excel. Cycle enabled. Cycle on Proms1Connection, Field Provider.
4. Edited report template, added table object (sense chart is a table, a simple list of Provider, wave, count), and dragged onto sheet.
5. Preview. Results as described above.
Thanks Lech
Your questions led me to create a super-simple version of the Sense app, for which the cycle filter worked. Further experiments showed the problem was an expression in the table which does not respond properly to filters in Sense. So now I know the problem that needs to be solved is in my work in Sense, not nprinting.
A couple of other learnings for me:
* when making changes in the Sense app, make sure to close it before reloading metadata in the Connection.
* for some reason my Sense app sometimes opens with a filter already set. I had inconsistent results when previewing my nprinting report. I worked around this by making sure the Sense app was open and no filters set before working in the nprinting report.
regards
Judith
Would yo ube able to:
It all depends how Qlik Sense app is build
Maybe there are some data island tables whichdrive normaly UI but in Qlik Sense they may not work
regards
Lech
Thanks Lech
Your questions led me to create a super-simple version of the Sense app, for which the cycle filter worked. Further experiments showed the problem was an expression in the table which does not respond properly to filters in Sense. So now I know the problem that needs to be solved is in my work in Sense, not nprinting.
A couple of other learnings for me:
* when making changes in the Sense app, make sure to close it before reloading metadata in the Connection.
* for some reason my Sense app sometimes opens with a filter already set. I had inconsistent results when previewing my nprinting report. I worked around this by making sure the Sense app was open and no filters set before working in the nprinting report.
regards
Judith
I usually connect nPrinting to published Qlik Sense apps so the BASE SHEETS are not editable and cannot change by accident as it would lead to many issues with further development.
I am under impression you linked your NPrinitng to app in your WORK stream - correct if i am wrong.
cheers
Lech
Yes, it's in my work stream, not published. This is my first use of nprinting, a proof of concept really. I'm using dummy data in a new/draft Qlik Sense app, which is probably why I hadn't noticed the error in my set expression.
So is it fixed now for you - if so - please mark CORRECT answer and therefore close this topic, thanks
Lech