This is one NPrinting 16 feature that will not make it into NPrinting 17+ platform.
QVW Reloads will need to be done exclusively on the QlikView/Publisher server as a QlikView reload task.
This in-turn can then be leveraged by a QVP connection to the QVW within your NPrinting connection 'server' configuration to ensure you have the most up to date data from the QVW for your NPrinting reports.
We are just 'like' you and like to be liked when providing a helpful answer. You may also press the 'Solution Accepted' button if an answer provided resolves your question or issue... Cheers!
The detail is that we are going to look like other platforms that all modules are independent and what we are looking for is to give users ease and that with a single task they can synchronize their information and not launch a task wait for it to end and then wait for it to end the other. in the night processes there is no problem but in the fiscal closures processes are needed tasks on demand but all in one. I put myself in the user's shoes, launch the process and only verify that I finish when the mail arrives, his work is analysis and not IT.
You can use NPrinting APIs that come with latest versions of NPrinting to enable the execution of an NPrinting Publish task after the reload of a QVW on the QV server. This requires customization and API development from the api library here:
If you need assistance configuring this solution (not included by default in the NPRinting web console), we can put you in touch with our Qlik Consulting team or other trusted Qlik Partners such as yourself..
There is an article about this for use with Qlik Sense, but you can use the same principles for QlikView as well.