Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
my goal is to generate an NPrinting report which contains an image of my dashboard but I have a problem launching my NPrinting reload task, in fact the data is not updating and I still have the same display even if the data on my dashboard changes.
The only way to be up to date on the dashboard is to manually reload the metadata but normally I shouldn't do this, do you have any idea where the problem might be?
Thanks in advance ! 🙂
Hi,
If you are using a connection to QlikView, when posting the question, please select the label QlikView, not Qlik Sense.
With local QlikView connections you have to reload the Qlik NPrinting connection metadata after the QVW reload in order to generate reports with updated data. Reloading the connection metadata will force all Qv.exe process to be closed and re-opened and this closes all opened QVWs and open them after with the updated data. It could be that sometimes you have correct data also without reloading the metadata but it is not deterministic. It is because the internal optimization algorithms closed all opened Qv.exe processes.
With connection to QlikView Server or Qlik Sense (only to Server is supported) you don't need to reload the connection cache before generating the reports. We suggest to use connections to QlikView Server instead of local also for this reason.
Best Regards,
Ruggero
Hi,
Are you using a connection to a local QlikView document?
The metadata reload can be scheduled by using the Trigger tab. So you can schedule the reload, estimate the duration, add a safety margin and schedule the publish task later.
Best Regards,
Ruggero
thank you for your reply ! 🙂
Yes I am using a connection that points locally.
So I created a trigger that will reload the application about 1 hour before my execution task starts, it is indeed a way to solve my problem.
But this is the first time I have this problem, it does not happen to me with my other reloading tasks, do you know what could be the causes of this malfunction ?
Hi,
If you are using a connection to QlikView, when posting the question, please select the label QlikView, not Qlik Sense.
With local QlikView connections you have to reload the Qlik NPrinting connection metadata after the QVW reload in order to generate reports with updated data. Reloading the connection metadata will force all Qv.exe process to be closed and re-opened and this closes all opened QVWs and open them after with the updated data. It could be that sometimes you have correct data also without reloading the metadata but it is not deterministic. It is because the internal optimization algorithms closed all opened Qv.exe processes.
With connection to QlikView Server or Qlik Sense (only to Server is supported) you don't need to reload the connection cache before generating the reports. We suggest to use connections to QlikView Server instead of local also for this reason.
Best Regards,
Ruggero