Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
pauljohansson
Creator III
Creator III

Nprinting doesn't refresh the data

Hej,

I'm using Nprinting 17.1.2 and. I'm experiencing a serious problem:

My Nprinting connection doesn't give me the latest data.


In other words, my Nprinting connection keep giving me the data of the .qvw from the point in time when the connection was setup in the first place.

Any pointers / ideas?

thanks in advance,

Paul

43 Replies
Daniel_Jenkins
Specialist III
Specialist III

Hi Stephen,

Use the Task Scheduler to run the batch file at a suitable time.

HTH - Daniel.

stig1984
Creator II
Creator II

thanks - I'll give it a go.

pablomind
Creator
Creator

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?

woutermak
Partner - Creator III
Partner - Creator III

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

Anonymous
Not applicable

  • Still not fixed in 17.3 ! It need a manual restart of Nprinting engine service or manual reload of metadeta from Nprinting webconsole to get the latest updated data, which is really annoying.
  • There is no bug fix of this issue in release notes of Nprinting 17.3, if anyone has a workaround to this issue kinldy share.
  • Solution by Mr. sjw is also not working.
Hatus
Partner - Creator II
Partner - Creator II

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.

Anonymous
Not applicable

Hi Hatus,

  • Yes you are right that after manually reloading the meta data, report shows the latest data but my view was different.
  • Example : What if client wants to distribute the created report from Nprinting in every 2 hours? Will he be manually reloading meta data after every 2 hours before running the scheduled report distribution task?
  • Is there any mechanism in Nprinting 17.3 from which the scheduled reports that has to be distributed should have the latest data without manual meta data reload?
Hatus
Partner - Creator II
Partner - Creator II

Hi Jahanzaib

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.

lindbergkarlsta
Partner - Contributor III
Partner - Contributor III

Hi all

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

Anonymous
Not applicable

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