Kindly note that this problem is NOT only regarding new objects being added and not appearing in the final report nor it is only about metadata not refreshing. This is about the objects in the model not being updated in NPrinting even though the source qvw file has been reloaded prior to running the NPrinting task.
The reports created by NPrinting will not use the updated qvw and the fresh data in it, rather reuse the report as it was when the connection was first created or as it was since last restart of the NPrinting services.
The main cause of this problem is that NPrinting server doesn't release the connection to the qvw file when it is finished.
There are 2 known ways to make NPrinting close the connection.
Solution 1 :Restart NPrinting services.
Solution 2 :Make a new one (let's call it Connection 2) and use this after finishing the first connection (Connection 1).
Steps:
- Connection 1 is connected to QVW 1 and Connection 2 is connected to QVW 2.
- Reload QVW 1 with new data (Data State 1).
- Reload QVW 2 with new data (Data State 1).
- Use Connection 1 to create an NPrinting report from QVW 1.
- Use Connection 2 to create an NPrinting report from QVW 2.
- Reload QVW 1 with new data (Data State 2).
- Reload QVW 2 with new data (Data State 2).
- Use Connection 1 to create an NPrinting report from QVW 1.
- Use Connection 2 to create an NPrinting report from QVW 2.
- The new NPrinting reports will both be with the new data! (Data State 2)
Important notes:
- When implementing this solution you must keep an eye on the memory consumption, and if there is any memory leak that accumulates over time.
Solution 3 :If the qvw document is hosted on a QlikView server, try to use qvp link instead of local qvw file connection.
This is due to a bug in the product. This should be fixed to work correctly both with qvp connections and local path to qvw in Nprinting 17.3.