So after reading all this I still have a question, Im using NPrinting 17.2.3 and set up my connection as a Local type for qvw file. If I reload my qvw document with new data, wont my report show the latest data?
There is an issue with the connection and refresh the data. This is solved in NPrinting 17.3.
Otherwise you have sometimes to restart the Nprinting services to get new data.
It’s better to upgrade to 17.3
I can totally confirm it. In 17.3 you have the bug fixed that when manually reloading the Metadata you now actually get new data. You couldn't get new data before even reloading metadata manually. I had to kill the QV.exe processes so that new instances can be started in the cache.
This job can't be automated neither. Clients need to manually generate new metadata every day for daily reports. A Reload Task like in NP 16 should solve this easily.
It has the same consequences. If the client needs refreshed data every 2 hours in a NPrinting Report. He needs to manually reload metadata every 2 hours. Sad but true.
In this case some clients prefer to downgrade to NPrinting 16, where this feature was still working.
Now it depends on the compatibility. NP 16 do work with QV 12.x but its not supported by Qlik.
Got this answer from Qlik Support today:
"As discussed, there's currently a limitation in Nprinting 17.3 where users are unable to see updated data when there's a change in the data content of the qvw application IF the connection to the qvw application is via local connection in Nprinting. This is caused because normally, Nprinting does not purge connections to a qv.exe process after it's initial opening of the Qlikview desktop application in the background.
There are 2 workarounds for this issue.
One of which is to use a qvp connection instead, and the other is to generate dummy reports but still use the local connection option.
A third option for this is to wait for the next release of Nprinting 17 which will be out after the middle of June. This update will have some additional option to end the qv.exe process after nprinting has finished generating a report or meta data, this will enable."
Does anybody know, if a ReloadTask for local qvw files is planned for NPrinting 17?
I think this goes hand in hand with the "data refresh" problem.
For me it's the the absolute basic basic (... basic ....) feature missing in NPrinting 17
For on demand reports, in my opinion it makes really no sense "torturing" the QlikView Server with permanent reloads for a report that is needed on demand by 2 persons a day with up to date data...