Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Troy1
Contributor III
Contributor III

Nprinting upgrade 16.9 to 19

Hi Everyone

We are about to make the jump out of 16.9 version. Can you please share your experiences. What should we look out for. 

 

  1. Would all the functionality of 16.9 work in latest version of NPrint.
  2. Do migration tool migrate everything?
  3. How does development different compare to 16.9, is it browser based development like QlikSense? 
  4. Anything else you can share. 
1 Solution

Accepted Solutions
Miguel_Angel_Baeyens

Following up on Lech's reply, let me also add 

  1. NPrinting Architecture: https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/DeployingQVNprinting/Architecture.h... and https://community.qlik.com/t5/Qlik-NPrinting-Documents/NPrinting-Architecture-Presentation/ta-p/1636...
  2. NPrinting Scalability: https://www.qlik.com/us/resource-library/qlik-nprinting-architecture-scalability
  3. Supported and unsupported configurations: https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/DeployingQVNprinting/Supported-unsu...
  4. Qlik Sense Object Support: https://community.qlik.com/t5/Qlik-Support-Knowledge-Base/Qlik-NPrinting-and-Qlik-Sense-Object-Suppo...
  5. QlikView Unsupported items, and more: https://community.qlik.com/t5/Qlik-Support-Knowledge-Base/Qlik-NPrinting-Unsupported-QlikView-Docume...

As any migration, there will be things that will have to be reviewed or rebuilt. NPrinting 16 was an add-on to QlikView and since NPrinting 17, the product is a standalone, multi server, multi thread engine with several different components interacting with each other. 

I would strongly recommend you to contact Qlik Consulting or a Qlik Partner or Professional such as Lech who will provide you with guidance and help you with the different steps in the process.

View solution in original post

4 Replies
Miguel_Angel_Baeyens

Must reads: 

To summarize, your questions:

  1. No. There are functionalities (such as linked fields, but also others) which do not work, or do not work the same way in 2019 versions than in NPrinting 16. It is important to note that NPrinting 17+ (therefore, any 2019 and 2020 versions of NPrinting) are a different product than NPrinting 16 used to be. They use services, a database for metadata and repository, certificates to communicate between services, etc.
  2. See links above for the content migrated. For example, connections did not exist in NP16 the same way they do in NP19+. Folders, filters are possible, but need to be generated first on NP19+
  3. It uses NPrinting Designer which is similar to the previous one, both in functionality and requirements. There are some new contents in the NPrinting Designer, see the release notes for the version you are going to upgrade to.
  4. APIs. A lot of stuff can be achieved using NPrinting APIs (plenty of examples in the links above) such as importing users, syncing users between Qlik Sense and NPrinting, calling NPrinting tasks from Qlik script, etc. relatively quick and simple.
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @Troy1 

@Miguel_Angel_Baeyens has provided you with practically everything you need to know, I want to point our few things which you will find in those documents but they might be in various places and can be easily missed:

  • you cannot assume you will just migrate - each and every report needs to be considered separately based on the solution it was using, like:
    • output format (for example: csv  from pixel perfect, html embedded from excel template etc.. -- not supported, but workarounds are possible)
    • was the report html embedded (if it was, what was the original template format (maybe excel?))
    • did you have users created with the same email (2 recipients sharing the same email)
    • did you have some funny logic when using filters  with (lock, select etc...) 
    • did you heavily used user filters (what filters - maybe bookmark filters)
    • did you have qvw with unsupported objects like (macros, always one selected, alternate state, triggers (sheets, on open etc...). NP 16 was more forgiving when those were present, with NP19 it is big "no-no!!!"
    • and many more....

What I want to say is that you need to be prepared and aware how things are working in NPrinting 19 vs NPrinting 16. So the first step is to go through documentation provided, (help.qlik.com, support articles, and Andrew's Playbook). This is just tip of the iceberg as those documents highlight the most important things. It may also happen that your reports are very simple and will practically migrate without issues - that is also possible, but it depends on how they are built.

 

now bottom line

I am not trying to scare you - I am trying to manage your expectations. Migration tool does great job - my comments on it here: https://nprintingadventures.com/2019/11/12/is-this-a-right-time-to-migrate-from-v16-to-v17-currently... still you need to know what you are doing.

On the positive side once you migrate I think you will be very happy with what you have. Much better product, much more robust with huge possibilities. Web based management console, API providing so much extra easy to implement solutions, and local client (designer).

If I were you I would first make sure I setup environment which is supported. There is a lot of requirements which must be met to have NPrinting 19 running properly. All of them are also listed on help.qlik.com. Once you have your environment up and running I would start migration from the simplest possible report. And would take it one step at the time. 

And at the end we are here to help... most likely by pointing you to https://help.qlik.com links where everything is practically documented 🙂

 

 

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Miguel_Angel_Baeyens

Following up on Lech's reply, let me also add 

  1. NPrinting Architecture: https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/DeployingQVNprinting/Architecture.h... and https://community.qlik.com/t5/Qlik-NPrinting-Documents/NPrinting-Architecture-Presentation/ta-p/1636...
  2. NPrinting Scalability: https://www.qlik.com/us/resource-library/qlik-nprinting-architecture-scalability
  3. Supported and unsupported configurations: https://help.qlik.com/en-US/nprinting/June2020/Content/NPrinting/DeployingQVNprinting/Supported-unsu...
  4. Qlik Sense Object Support: https://community.qlik.com/t5/Qlik-Support-Knowledge-Base/Qlik-NPrinting-and-Qlik-Sense-Object-Suppo...
  5. QlikView Unsupported items, and more: https://community.qlik.com/t5/Qlik-Support-Knowledge-Base/Qlik-NPrinting-Unsupported-QlikView-Docume...

As any migration, there will be things that will have to be reviewed or rebuilt. NPrinting 16 was an add-on to QlikView and since NPrinting 17, the product is a standalone, multi server, multi thread engine with several different components interacting with each other. 

I would strongly recommend you to contact Qlik Consulting or a Qlik Partner or Professional such as Lech who will provide you with guidance and help you with the different steps in the process.

Frank_S
Support
Support

hello @Troy1 

Also visit NPrinting 16 to NPrinting 19+ Migration Playbook - Qlik Community - 1780278

 

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!