topic Re: NPrinting refresh 17.3.1 in Qlik NPrinting

NPrinting refresh 17.3.1

Mon, 19 Jun 2017 05:39:49 GMT

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!!!

Re: NPrinting refresh 17.3.1

Lech_Miszkiewicz — Mon, 19 Jun 2017 05:54:14 GMT

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

Re: NPrinting refresh 17.3.1

Mon, 19 Jun 2017 06:05:50 GMT

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.

Re: NPrinting refresh 17.3.1

Lech_Miszkiewicz — Mon, 19 Jun 2017 06:19:43 GMT

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

Re: NPrinting refresh 17.3.1

Stephen_Jasionowski — Mon, 19 Jun 2017 16:14:40 GMT

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.

Re: NPrinting refresh 17.3.1

Anonymous — Mon, 19 Jun 2017 16:53:52 GMT

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

Re: NPrinting refresh 17.3.1

Lech_Miszkiewicz — Tue, 20 Jun 2017 00:18:28 GMT

No - it does not.

Re: NPrinting refresh 17.3.1

Anonymous — Tue, 20 Jun 2017 16:44:04 GMT

ok thanks for your answer...

Re: NPrinting refresh 17.3.1

amweiner — Wed, 28 Jun 2017 21:40:58 GMT

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?

Re: NPrinting refresh 17.3.1

Lech_Miszkiewicz — Wed, 28 Jun 2017 21:56:17 GMT

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

Re: NPrinting refresh 17.3.1

amweiner — Thu, 29 Jun 2017 03:05:14 GMT

I guess I need to restate my question... in 17.3 and earlier, you had build reports based upon server connections as opposed to local connections for reports to update when data in the qvw has changed (after reload). Will 17.4 support update of reports based upon local connections when data in the qvw changes? I didn't see anything about that in the 17.4 release notes.

Re: NPrinting refresh 17.3.1

Lech_Miszkiewicz — Thu, 29 Jun 2017 03:31:37 GMT

Hi Ann,

logic of local connection has not change. As long as you have a session open that long the new data will not come in. That is a standard behavior of QlikView. Generete metadata trigger is meant to be use as a supporting feature so - say at night - metadata get refreshed and all new objects are available when developers will start work.

You can use a trigger for metadata to re-instate a QV.exe process in order to re-open Qv document using local connection.I do not see any value in it however as those 2 process will be detached. There is no build in solution to link them all up in a chain reaction process like: Reload qvw --> Reload -metadata --> Publish NPrinting report

There may be available API - but i am not familiar with them.

..... and again i strongly recommend using qvp connection for performance and stability reasons!

What is the reason that you need to use local connection to document Ann?

regards

Lech

Re: NPrinting refresh 17.3.1

Ruggero_Piccoli — Thu, 29 Jun 2017 10:49:06 GMT

1 - Open the connection you want to trigger

2 - Click on Triggers and se the trigges you need

Re: NPrinting refresh 17.3.1

amweiner — Fri, 30 Jun 2017 14:35:24 GMT

Lech,

We use local connections because the server connections, in earlier versions of Nprinting, were slow to generate (sometimes taking hours) and producing errors we could not resolve. I am in a unusual environment where I don't have access to log files nor do I get timely support from the administrators to help with troubleshooting. The lack of transparency made troubleshooting impossible. So, to make progress on report design, I have been using local connections. I am hoping with 17.4, I will be able to see errors more easily and will take advantage of the new trigger feature. I will encourage our administrators to upgrade as soon as possible.

I think that it odd to have a feature such as generating local connections that is only useful for report design, but not clearly documented that is its only purpose. Maybe on the Connections page, there should be a message explaining that. I did not see that documented in the on line documentation. Perhaps I missed it.

Re: NPrinting refresh 17.3.1

amweiner — Fri, 30 Jun 2017 14:36:09 GMT

Thank you. I will urge our administrators to upgrade and I will try it.