Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Not applicable

NPrinting refresh 17.3.1

Dear all

  My NPrinting use local connect to qv,but these data don's refresh

  Could you tell me how automatic refresh to data and send new e-mail for user?

  thanks!!!

14 Replies
Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting refresh 17.3.1

Hi Wood,

Few questions to start with:

  • why are you using local connection?
  • how is your QVW file reloaded?
  • Is it possible to use QVP (preferred connection)
  • What do you mean "these data does not refresh" - do you mean data in your NPrinting report?
    • Does data in your QVW refresh? What triggers it?

answer above questions and we will take it from there.

cheers

Lech

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.
Not applicable

Re: NPrinting refresh 17.3.1

Hi Lech,

Thanks for your reply !

1,We have installed NP and  QV in same machine;

2,We set up a reload schedule in QMC

3,Can it use qvp connection if NP and  QV installed in same machine

4,Yes,Nprinting report does not the lastest data (QVW data have refreshed)

Best regards.

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting refresh 17.3.1

Yes - you can use QVP connection even if you have NP and QV installed on the same box. Using QVP will solve your issues.

There is A LOT OF DOCUMENTATION on community how to establish QVP connection and how to troubleshoot it.

try it - and then let us know how it goes.

regards

Lech

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.
Employee
Employee

Re: NPrinting refresh 17.3.1

With the upcoming release this month, you will be able to make the metadata reload a scheduled job. So you ca run the refresh prior to any reports that you run, ensuring that you have refreshed data in the report.

This will work for local QVW connections and others.

roharoha
Valued Contributor III

Re: NPrinting refresh 17.3.1

does that mean that the local qvw itself will be reloaded?

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting refresh 17.3.1

No - it does not.

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.
roharoha
Valued Contributor III

Re: NPrinting refresh 17.3.1

ok thanks for your answer...

amweiner
New Contributor III

Re: NPrinting refresh 17.3.1

Just to clarify... there are two different things going on: (1) Reloading the qlikview document itself (through reload tasks in QMC) (2) reloading the metadata when a qlikview document contains new data (after the qvw has reloaded).

So, in July 2017 release, will Nprinting have an option to reload the local connections metadata on a regular basis? And will this option be available in QMC or through Nprinting Admin? And if it available through Nprinting Admin, how could one coordinate the reload of the qvw with the reload of metadata?

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting refresh 17.3.1

1 - reload qlikview document - this is not available

2 - July release is out - try it. It has a "TRIGGER" property on generate metadata task. It is controlled in NPrinting ADMIN console. I do not see any reason to coordinate reload of qvw with metadata reload. Metadata reload should be done only if you have new object (table, field, chart etc in your qlik app), otherwise you do not have to do re-generate metadata. New values in you QLik app after reload will flow through to NPrinting even without re-generating metadata cache.

regards

Lech

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.
Community Browser