Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
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
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?
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
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.
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