NPrinting on demand report generation button extension migration between environments

[NarayanaSwamyKarli]

Hi,

We use Qliksense Nov 18 and NPrinting Nov 18 versions. And, we use NPrinting on demand report generation button where we configure the NPrinting app, connection report and format to print nprinting report from button click.

When we develop Qliksense app, we use on demand button which points to NPrinting Dev server which will list the DEV nprt apps, connections, reports in the drop down.

So, when we migrate qliksense app from DEV to UAT, we cannot just migrate as it is as button points to DEV nprt.

So, tried just changing nprt DEV to nprt UAT link and migrated qliksense app.

But, its not picking up the nprt App, connection , report in UAT and now I cannot edit the button in UAT to configure according to UAT nprt.

When I duplicate sheet and edit button, I can configure, but cannot make these change applied to published sheet as sens app migration needs to go through svn and deployment tools

Please assist how to handle migration in this case.

[Frank_S]

Hi @NarayanaSwamyKarli 

Please check the following article.

https://support.qlik.com/articles/000078157

There are known issues around that process unfortunately. A fix was introduced in the June release that is mentioned in the article.

If you continue to see the issue after following the article, please start a new support request with the Qlik Support Desk.

In the meantime, there is no simple workaround but you can try the following:

• Export the report template from DEV to UAT NPrinting within  the NP web console/Reports area using https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/AdministeringQVNprinting/Impor...
• When importing the report to UAT, import the report as v2 ie: myOnDemandreportv2
• Add a new on demand button in your QS app and connect to the newly imported report in UAT.

I realize this is NOT ideal but since you asked for a workaround, this is what I have at this point to share in addition to the aforementioned article. Also this means that you actually have two different reports in the meantime. 

So I suggest upgrading as per the article to make the process more fluid. However, please note that there is another On Demand issue that is affecting 'some' users where v2.12 appears rather than v2.13 that should appear in the Qext file. This is also being resolved in Nov. 2019 release of Qlik Sense...just fyi...so you may wish to wait for that as well. 

I apologize that I cannot give you better news at this point but that hopefully you are fully aware of the issues now an a possible short term (albiet not great) workaround.

Others here may also have some guidance with other potentially unique, scalable interim workarounds.

Kind regards...

cc @Ruggero_Piccoli