Nprinting 18 - Maitenence

[amehta]

Hello Everyone, We are moving from nprinting 17 to N printing 18.  My findings are the new npriting server is fast multi threaded however the maintenance is going to be a night mare.

Below is our use case scenario. Please let me know if anyone of you has already solved for it or has an idea.

1. We have around 100 Apps. 

2. Every app has mostly same reports. The logical reason for making these apps separate is due to the data.

3. Now if we need to add a new variable to n priting in the old npriting we used to use command line operations to copy the variable to every one across the board. we keep our nprinting file common

Now in the new approach we dont know any way to copy the variable across all reports.

[Frank_S]

If you are upgrading from NP 17 to NP 18, then you should see no measurable differences other than improved performance and many bug fixes. They are otherwise essentially the same 64 bit platform (not the 32 bit platform).

However if you are moving from NP 16 (client server 32 bit version) to NP 18 (64 bit version) Then you should review the following links before upgrading. You might even want to consider evaluating and testing NP 18 prior to moving to to ensure that important gap features that you need have been added. These two are completely different platforms. See the migration link below for more information.

Migrating from NP 16 to NP 18
https://support.qlik.com/articles/000029513


NP 18 gap list (scroll to the bottom of the page)
https://help.qlik.com/en-US/nprinting/November2018/Content/NPrinting/Introduction/Introduction.htm

[amehta]

Thank you for the response, we are evaluation the new nprinting version.

Is there a way we can directly add variables to a report using a API call? so if we have one variable add it accross to all reports using a program?

[Frank_S]

There is a library of available API's.
I don't see an API that meets your specific requirement.
https://help.qlik.com/en-US/nprinting/November2018/Content/NPrinting/Extending/Intro-Extending.htm
https://help.qlik.com/en-US/nprinting/November2018/Content/NPrinting/Extending/NPrinting-APIs-Refere...

Also it's not clear exactly what your previous method was in 'old nprinting' (not sure what version you are referring to here either) via command line.

Perhaps is you explain exactly the steps to reproduce what you did in the 'old nprinting' and the exact version of 'old NPrinting' you are referencing and what you hope to accomplish in NPrinting 18 and higher versions, myself or someone else on this board may be able to provide feedback on your specific requirement if you can provide these additional details.

[Ruggero_Piccoli]

Hi,

There is also an update chapter in the release notes of the version you are installing.

About variables, please open a different conversation for each query.

Best Regards,

Ruggero

[amehta]

Thank you for your response.

We currently use n printing 16.5. Below is our current folder structure and Process. we make nprinting change in the common structure and copy that nprinting use command line arguments to all the clients. This reduces our maintenance work as we don't need to edit each client nsq and add the variable.

COMMON -- QVW/NPRINTING

 Client 1 -- QVW, NPRINTING

Client 2 -- QVW NPRINTING

Now int he new prinitng we are not sure how to do this ? we have 100 client folders, editing each client and adding this variable will become a huge maintenance effort.

[Ruggero_Piccoli · Accepted solution]

Hi,

Migrating from 16.* to 17+ is a complex project. You need to evaluate if 17+ has all features you are using in 16, you need to manually reacreate the connections to QlikView documents and import the reports template one-by-one. Also tasks must be manually recreated because right now (February 2019) there is not an importing tool.

Distribution to user folders and subfolders is supported by Qlik NPrinting 17+ and folder and subfolders can be imported for each user via Excel file in an import task. 

My suggestion is to install a Qlik NPrinting 17+ (latest version is February 2019) in a test computer, study the online help site and test your migration from 16 befor to go live in order to solve any problem in the migration path.

Best Regards,

Ruggero