Hi Emmanuelle - I think i have described the problem you have in my previous posts.
down to your question re NP June 2017 - It has a trigger implemented to refresh metadata. So if you are using "Local" connection to QlikView document a trigger will actually allow you solve this issue as it will kill a QV instance on certain schedule and re-open new one for this connection - which at the same time will update data you need. From this perspective NP June 2017 resolves your problem.
still - I recommend using QVP connection for performance, stability reasons. That would solve this problem also in older NPrinting versions. Local connections will be much slower and will consume a lot more resources.
cheers Lech When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
I'm having the same issue, I think NPrinting just don't refresh the data. This is a serious problem because the Task will be sending the same report everyday. I'm finishing a project on NPrinting and this limitation is really annoying for us and the client.