I tried 17.2.1 open-minded, never tested 17.3.
The installation itself was problem-free.
Besides a few bugs I found within 1 testing week,
there are some NP16 features missing, that I use extensively:
- trigger reload for local qvw file
- clone elements in web interface for testing (filter, task, report, ...)
- using QV variables within mail text and subject line
Another important fact:
The main difference between 16 and 17 is that in 17 everything will be stored within one repository.
So you are not able the make a copy of an nsq file like you did in 16 and manipulate it for testing reasons.
... just my personal thoughts
I'm still on QV 11.2 .. Tried to switch to QV 12 once when the left join in the script was broken ! . Had to reinstall everything
I'm really afraid too to switch to the new generation of Qlik tools. Installation problems, one repository, what made Qlikview better and easier to admin than any other pro tool seems to be gone.
I understand it's better to start with the newest version but I'm afraid to lose time.
I would recommend installing v17 on its own server without any other Qlik server products and just Qlikview desktop installed.
I would also be aware that in the near future Qlik will end support for v16 so you will have to go through the pain of upgrading everything.
For a new install I personally wouldn't build an estate of reports in a product that is being sunsetted.
Just my opinion though.
I absolutely agree. Yes, it basically makes no sense using NP16 anymore.
But I think that it is very dificult to place, that a newer version of a product supports less features then its predecessor.
At the moment it is not possible for me using NP17 due to the lack of missing features.
I was not able to build the same reports in NP17 , regardless of how much time I invested.
... just my personal thoughts
it's exactly the same between Qlikview and Qlik Sense.
Qlik had first released Qlik Sense as an upgrade to Qlikview (Qlikview Next). But when a new tool lacks great features, customers cannot forget everything and switch to the new tool .. It became Qlik Sense and they said they would remove Qlikview after a few years. I don't think the same policy exists now as Qlik Sense doesn't fit most users needs
Totally agree Robin as you have invested time and effort into v16 with features v17 doesn't support.
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.
However for a new install I would certainly go with v17, you eliminate the possibility of creating new reports with missing features and will continue on a product path that Qlik are investing in.
It's also easier to explain to end users that the product 'doesn't do that' rather than 'it did do it but we can't anymore'.
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.
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.