Nprinting 16 or 17 for Qlikview

[fredericvillemi]

Hello,

We have just bought NPrinting and I begin having installation problems with 17.3. I remember the times when installation a Qlik product was easy, it's not the case anymore !

Last year, one guy in Qlik had adviced me to stay with v16 because the v17 was not ready.

I'm afraid I will lose time trying to install v17.3, making ticket because the installation doesn't work correctly, and I would like to know if people are still using v16 ?

If I'm only using Qlikview to make reports, is it a good idea to stay in v16 while waiting to have a good v17 or is the v17 far better than v16 and I should go to it because everything missing has been added and it works great ?   Honest advices please

[Anonymous]

You should be OK on a test server but may get possible issues with your Sense / Qlikview server installation.

Its frustrating but stand alone NPrinting is the only way I have got v17 working stable with Sense and Qlikview Server.

[Anonymous]

"Most if not all the missing features are on Qlik's roadmap and I'm sure they will not discontinue v16 support until the new product is at least equal in its offering."

--> I hope so

[mkelemen]

Hi Frederic.

is the v17 far better than v16 and I should go to it because everything missing has been added

No and no.

The v17 is not better by any means in terms of report creating. The architecture under the hood changed (to work with sense I assume) and they are slowly catching up with the functionality.

Also the new web interface is pain to work with (no copy/paste).

We are facing similar decision but we already have a lot of reports created which use some of the functionality that has not been ported yet. We could probably create workarounds if necessary but it would be a lot of work. So we are staying put and hoping that it will be implemented in 17 soon.

Your advantage is that you do not have the existing body of work and can start fresh without losing much.

BR,

  Matus

[ngulliver]

Hi,

I think it may also be worth noting here that there is no upgrade path between 16 and 17. Also, Qlik announced some months ago that the end of support for v16 will be February 2018.

Whilst I have found 16 far more stable and more feature-rich there may be no business rationale to go with anything earlier than 17.

Cheers,

Neil

[#6]

Hi,

its already a half a year old thread but so far its still relevant:

We also bought a year ago Nprinting to replace an very unstable reporting system (Crystal Delivery on old XP machine). But so far we did not really use it, as the version 17 does (still) not fit (all of) our needs. For very simple reports we can use it, but so far many basic features are not there:

- the product is called Nprinting but cannot print directly to a printer

- more options for scheduled execution (monthly, yearly, etc)

- Cycling reports

- clone reports

- buggy

- ...

I got the info that the developer team wants to release a new version every 10 weeks. Next should be planned for September 2017. If not anytime soon the needed features come to v17 I need really to think about to use v16. They still releasing new versions (and supporting v12.1 of QlikView) and the support was already extended till December 2018. In my opinion Qlik should publish a roadmap when they plan which features roughly come to v17.

Surely its not easy to write such a big program like this from scratch in few months, but still.......

Let's hope the next release brings some of our needed features

Cheers

Roland

[Ruggero_Piccoli]

Hi,

- cycling reports

- import/export (so you can export a report and create a new one from the exported one so it is the same as cloning)

are both part of next release September 2017. You can download a technical preview from Qlik NPrinting September 2017 Technical Preview. This is a preview not for production use. The related final version will be publicly available in September.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

[#8]

Hi,

thanks a lot!

Best regards

Roland

[Lech_Miszkiewicz]

I see NP 17 as the product i would go with.

I know it goes through difficult days now, but at the end it will be the product Qlik will go with forward. If it is small setup you are thinking about you can start with v16, but i f you are aiming in creating 20+ reports, one day soon yo uwill have to build them all from scratch in NP17. I do not think it is worth extra work.

cheers

Lech

[#10]

Hi,

yes i am thinking the same and we are still deciding what to do. Normally in QlikView things were growing fast in the past, so probably with NP would be same . Everyone wants new stuff 🙂   So we still keep alive our old system as long as possible and start slowly with easy reports in v17. When the time is ready we can move all old stuff to the new system. Our consultant told me the developers want to push a new version every 10 weeks, so something should be expected in near future.

I read that the swap from v16 to v17 is also not so easy so......

Best regards !

Roland

[fredericvillemi]

Hello Lech,

You are probably right. But I'm afraid I don't trust Qlik anymore on new products.

Releasing a V17 of Nprinting without the cycling feature seems incredible for me.

I'm happy to see that the new version will be released in september and will include everything but I will wait to see if everything works as expected and I prefer doing my 10 reports twice instead of waiting months to have the new version of the tool I bought as good as the previous version.