Nprinting does not pick latest data

[sandeepgather]

We have an Nprinting report which has been running for a long time. Off late we are seeing instances where Nprinting does not pick the latest data. However, when it is re-run then their is no issue and data is reflected correctly.

Currently we have setup an API based trigger which runs the Nprinting job as soon the Qlik sense App refresh is complete. Any pointers what might be causing this.

We are on Qlik NPrinting April 2020

Qlik NPrinting 

[Lech_Miszkiewicz]

Hi @sandeepgather 

1. I gather you are on Qlik Sense September 2020 or older - right? If not, make sure you are on compatible version as documented 
   1. "The following Qlik Sense versions are supported when connecting to Qlik NPrinting. Note that your Qlik NPrinting version must be equal to or higher than your Qlik Sense version"
   2. https://help.qlik.com/en-US/nprinting/September2020/Content/NPrinting/DeployingQVNprinting/System-re...
2. When you say:"Currently we have setup an API based trigger which runs the Nprinting job as soon the Qlik sense App refresh is complete" it means that you have SEPARATE APP which releads as separate task after the app preceding it finished reloading and only then triggers NPrinting via API?

Obviously we would need to know the exact details if we were to learn more or advice more, but the above 2 points are absolutely critical and given that you are way outside of currently supported version it is hard to add anything else to it.

cheers 

[sandeepgather]

Thanks Lech

We are in the process of migrating to Power BI so don't have the option to upgrade. We had this setup running for around 5 years without any issues.

We have a Qliksense App which checks whether the Sales App is refreshed. Once Sales App is refreshed it will trigger the Nprinting task as the Nprinting report is based on the data from Sales App.

[Lech_Miszkiewicz]

HI @sandeepgather 

it does not matter if it was working before or not... what matters is if you are running compatible setup? If not then all I can say is that you were lucky it worked before and that you are unlucky it stopped working now, but that is exactly the very nature of unsupported configuration! So once again I am asking the same question:

Are you running compatible version of Qlik Sense with your version of NPrinting? If you are not sure just tell me what exact version of Qlik Sense you are currently running on and we will take it from there. I am also not bothered if you are out of supported version as only thing we need to make sure is the compatibility between Qlik Sense and NPrinting.

If you have upgraded your Qlik Sense without considering NPrinting then sorry to say but that is common mistake and I have seen it many times which then means we cannot guarantee that anything will work. All we can do is just try things....

Lastly as a wokaround in your API Trigger app you could stick in piece of code forcing NPrinting connection to regenerate metadata for that app which normally would reset state of the app to the most up to date version. There is rady to use subroutine you can explore here: https://nprintingadventures.com/2019/04/08/nprinting-api-qlik-rest-subroutines/

cheers

[sandeepgather]

Sorry, I forgot to provide the other details earlier.

Qlik Sense May 2021 Patch 5

Qlik NPrinting April 2020

I will try the workaround and update.

[Lech_Miszkiewicz]

RIght - so:

1. not compatible configuration.....
2. .... and label used for this post should be updated to show April 2020 as currently it shows September 2020 which is confusing 

Otherwise what can I say - you can try implementing the qvs library which then would be very simple:

// Authenticate

Call NP_Authenticate;

// Get AppId by Name

Call NP_GetAppID('$(vNPrintingAppName)')

Drop Table apps_items;

// Get and Reload Connections

Call NP_ConnectionReload('$(vNPrintingConnectionName)','$(vNP_ReloadDuration)')

// Get Task

Call NP_GetTasks('$(vNPrintingTaskName)')

// Trigger Tasks

Call NP_TriggerTasks

// Clean

Drop tables

task_items

,connection_items

,_post_items

;