Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I recently switched from NPrinting 16 to NPrinting May 2023 SR3 and QlikView May 2023 SR1. My QVF/QVW document gets refreshed daily on the QlikView server.
Initially, I noticed that my NPrinting report worked once, but the next day it was sent empty (charts and tables were present, but no data). After tinkering in the NPrinting web console, it worked again once, but then the next time it was empty again.
Later, I discovered that I needed to schedule a metadata refresh to run before the publishing task. Is this the correct approach, or am I doing something wrong?
If scheduling a metadata refresh is necessary, is there a way to automatically trigger the report publishing right after the metadata gets refreshed?
Thanks for your help!
I'm not sure if this is relevant or not. The data in the report is dependent on a date parameter that gets passed from NPrinting filter which is usually today(1)-1 with evaluate ticked.
Hi, metadata only needs to be refresh when there is any field change or change in data model.
need to check with your date Parmeter is filtered properly with format as well as with data.
If you use NPrinting QVP connections you should see less need to reload your NP connections.
I presume you are currently using Nprinting local connections based on the description of your issue.
Now if you want to perform reloads based on another event you can use NPrinting API's but that is a larger discussion.
You can visit these links for more information.
You can use QlikView QMC (publisher required) event based task triggers to reload your NPrinting tasks and connections. (APIs can be used in both QlikView and Qlik Sense).
Kind regards...
You are right, I'm using a local connection to the document. If I understood correctly, my easiest option is to time the metadata trigger and the publishing task trigger to run consecutively with enough time in between to avoid sending the report empty. Unfortunately, we are not running QlikView Publisher.
Hi @AHMB - You are overthinking it i think 😄
There are really 2 things you need to ensure:
1. run your connection as QVP or Claster connection!! Local connection is terrible practice anyway and sooner or later would cause resource issues for obvious reasons (by using local QlikView apps there is 0 control over resources used).
2. make sure your QV app is already reloaded. To achieve this point you can use API embeded and create task chaiing which will trigger NPrinting only after QlikView is reloaded: https://nprintingadventures.com/2019/04/08/nprinting-api-qlik-rest-subroutines/ This link has other links in it with description how to set everything up.
THERE IS NO NEED FOR PUBLISHER TO ACHIEVE ABOVE!
Thank you Lech,
I will try this after I resolve the QVP connection issues.
no worries - lets see how you go.
cheers
what is your QVP connection issue?
it is described in the other community post: https://community.qlik.com/t5/Qlik-NPrinting/QlikView-Server-is-unreachable-from-NPrinting-Web-Conso...
cheers