Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear all,
For a project within my work I need to generate an NPrinting report. I have experience in Qlik View, but NPrinting is new for me. Also my direct Qlik colleagues have not done that much yet in NPrinting.
The goal of the NPrinting report is that users can easily get a status overview of their project on a weekly base or on demand. Couple of questions from my side:
Thanks,
Spiller
Hi,
I suggest you to start by reading the official help site at https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/Introduction/Introduction.htm. There are a getting started tutorial and also videos for each main feature.
About your question:
Best Regards,
Ruggero
Hi,
I suggest you to start by reading the official help site at https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/Introduction/Introduction.htm. There are a getting started tutorial and also videos for each main feature.
About your question:
Best Regards,
Ruggero
Hi Ruggero,
Thanks. So for the reload of the data within the QVD it will always need to go via the Qlikview side.? That can't be triggered via NPrinting?
Regards,
Spiller
One more question: Can On Demand be triggered for a QVW that's not visible for the end user at the front end? And how to link that on demand report then to the correct front end dashboard?
Hi @Spiller
NPrinting does not have a qvw reload functionality so qvw reload needs to be handled by QlikView side
Now I am not sure about QlikView OnDemand and I have no environment to test this, but in Qlik Sense you can build app which you can use as UI/selection app for your OnDemand NPrinting reporting. That app should maintain the same associations between all fields you are wanting to use as filter selections so whatever you are selecting in your app is possible to be selected in the app where NPrinting report comes from. With Qlik Sense that selection gets passed via api to the source app based on connection used in report so there is no need to link it in anyway. In QlikView though it may be different technology used and I cannot guarantee if it will work.