topic Re: Qlikview vs Qliksense - segmentation or replacement? in QlikView

Qlikview vs Qliksense - segmentation or replacement?

davdiste — Fri, 13 Jul 2018 09:25:44 GMT

Hi all,

Several IT providers in the last period are changing their offering from Qlikview to Qliksense.

Among the motivations IT providers give:

- Qlikview is becoming obsolete

- Soon Qlikview will be dismissed

- Qliksense is smarter

- Is more efficient to concentrate the training of technical skills on one of the two solution

In your opinion, which of the following statments is more true and why?

1) Qliksense will replace Qlikview. The aim of the solutions is the same and Qliksense is more aligned with the business needs of customers

2) Qlikview and Qliksense are different. An IT partner capability to provide BI projects based on both solutions is a point of strenght

Re: Qlikview vs Qliksense - segmentation or replacement?

YoussefBelloum — Fri, 13 Jul 2018 09:40:46 GMT

Hi,

The best you can do is answer the question yourself and choose what is true and what is not.

but to be able to do that, you have to know very well both solutions or at least read experts articles/reviews/opinions comparing these 2 powerful tools. simply type Qlikview vs Qliksense on google will take you to the best links

Good luck

Re: Qlikview vs Qliksense - segmentation or replacement?

davdiste — Fri, 13 Jul 2018 09:45:36 GMT

Hi,

I've my opinion, but I want to know the general opinion of other pratictioners.

Thanks anyway.

Re: Qlikview vs Qliksense - segmentation or replacement?

YoussefBelloum — Fri, 13 Jul 2018 09:57:53 GMT

so maybe stevedark‌ mto‌ rwunderlich‌ can help you on this

Re: Qlikview vs Qliksense - segmentation or replacement?

stevedark — Sun, 15 Jul 2018 10:42:53 GMT

Hi,

I've put various thoughts on this topic on my blog, one such post is here, and there are links to others from within there:

https://www.quickintelligence.co.uk/qlik-sense-apis-mash-ups/

There are certainly things that QlikView can do better and quicker, the ease of dropping all fields into multiboxes (for example) makes exploring a new data set a breeze. The Insights button in the latest version of Sense is clever, but it is no replacement for getting as much of the data as possible in a reasonable amount of space as quickly as possible.

The flip side is that the reasons for not using Sense are getting fewer and fewer by the release. The feature gap that existed at first is closing. There are also some compelling reasons to use Sense, beyond the flashy responsive UI, the integration of chunks of GeoAnalytics into the base product springs to mind as a differentiatior.

QlikView is a brilliant product and will be around for some time yet. Qlik are committed to supporting it for just that reason. The direction of travel is definitely towards Sense though.

As a consultant if you have both in your kit bag then I would say you are at an advantage. If you are coming to it fresh though, with no experience of either, then I would definitely say you should focus your efforts entirely on becoming expert in Sense.

A slight caveat on that though, the best documentation I have seen on some core topics, like data modelling and Set Analysis, pre-date Sense. These features are identical between the products, and reading up on the parts of QlikView that you can cross apply is a very good idea.

Sorry, that is probably a more long winded answer than you were after.

Hope it is of interest though.

Steve

Re: Qlikview vs Qliksense - segmentation or replacement?

YoussefBelloum — Sun, 15 Jul 2018 20:51:57 GMT

Thank you for your time Steve

Re: Qlikview vs Qliksense - segmentation or replacement?

hic — Mon, 16 Jul 2018 07:23:12 GMT

Davide

I am currently working in Qlik with Product Design, and my area of responsibility is "Advanced Authoring". My directives are simple: Get advanced features into the product; both advanced features aimed at a document developer and advanced features exposed in user-friendly ways so that a business user can use them.

So, we are not (only) talking about self-service. We are talking about e.g. all the useful features that QlikView has, but Qlik Sense hasn't: Buttons, Actions, Calendar object, Always one selected, Alternate states, Accumulations, etc.

My personal view is that we should make Qlik Sense be able to do everything that QlikView can do - and more. In the future, it should be possible to use Qlik Sense both for guided apps (prepared documents built by data experts) and for self-service (work by business users). But you should of course also be able to combine the two, so that a business user can do self-service in an advanced app built by an expert. Then the business user will stand on the shoulders of the data expert.

So, my answer is a clear 1).

HIC

Re: Qlikview vs Qliksense - segmentation or replacement?

tresB — Mon, 16 Jul 2018 07:33:06 GMT

So I was not that wrong: Why not make Sense a superior version of View

Re: Qlikview vs Qliksense - segmentation or replacement?

stevedark — Mon, 16 Jul 2018 07:47:45 GMT

Wow! Thank you to for pointing me to comments I made nearly four years ago. Funny how the passage of time can change some things but others remain the same.

Interesting to see my point about having a sensible way for customers to have both QlikView and Sense is finally being realised with the move to bring in a Dual Use licence.

The point about the products being two distinct things that shouldn't be compared and fulfil different use cases is still true today, but HICs comments (which I will come back to...) suggest that this may start to be eroded somewhat.

Re: Qlikview vs Qliksense - segmentation or replacement?

Peter_Cammaert — Mon, 16 Jul 2018 08:02:42 GMT

I keep hearing louder (now even from execs) that Qlik is targeting real feature parity between QlikView and Qlik Sense. While it seems sensible to me to go for Qlik Sense when a company is just starting with intelligent BI/Business Discovery, we may see Qlik eliminate all objections against simply switching from View to Sense within the near future. Which was and still is a bit of a no-no at the moment for companies that have invested heavily in turning QlikView into a business-critical asset.

The future is bright, I'm sure !

Re: Qlikview vs Qliksense - segmentation or replacement?

davdiste — Mon, 16 Jul 2018 08:11:53 GMT

Hi Steve,

I've appreciated your comment and I'm reading your topic on th blog.

Thanks

Re: Qlikview vs Qliksense - segmentation or replacement?

davdiste — Mon, 16 Jul 2018 08:32:59 GMT

Thanks Henric for the answer,

Your opinion for me is more than important, maybe the more important.

Is really hard to get used to answer 1), Qlikview in the last 4/5 years gave me a lot of satisfaction (and is giving a lot of satisfaction my customers too).

Best regards.
Davide

Re: Qlikview vs Qliksense - segmentation or replacement?

hic — Mon, 16 Jul 2018 08:54:40 GMT

QlikView is still the more mature product, and I too - just like many of our customers - use QlikView a lot. So we need to support and improve QlikView for many years to come. And we will.

But that shouldn't stop us from making Qlik Sense better, so that more and more customers choose to use Qlik Sense. Also, we are making it easier to have a mixed environment (having both QlikView and Qlik Sense) and re-using resources for both. Only this way can we support the BI journey of our customers while focusing our development efforts on modern technology.

HIC

Re: Qlikview vs Qliksense - segmentation or replacement?

davdiste — Mon, 16 Jul 2018 11:33:49 GMT

Thanks Peter

Re: Qlikview vs Qliksense - segmentation or replacement?

stevedark — Thu, 19 Jul 2018 09:29:42 GMT

Hi Henric,

I'm pleased to hear that regarding bringing more and more of the features of QlikView through into Sense, and that this is where Product Design's head is at.

My slight confusion with this though is if this is the objective why has it simply not been done over the past couple of years?

You mention Buttons, so let's take that as an example. There is an excellent extension for this available on Qlik Branch. Written by Qlik's very own Stefan Walther. We both know that this extension is going to be stable and well thought through. With Stefan being on the team there, Qlik has the perfect opportunity to sort the commercial and technical arrangements to make that extension part of the core product, rather than one I have to download and install separately at each site I deploy to.

If there was a real desire from Qlik to move toward feature parity of the products I can't see why we still do not have buttons.

Whilst other features are drip feeding through (variable column headings a couple of releases back and condition columns just recently), there are some real blinding omissions - a straight line trend through a line chart is one I have mentioned to you previously.

I am playing devil's advocate here a bit, as I do know a little about the challenges in achieving these things, and what your own opinions are on some of the issues. I do think though that more clarity needs to be given to the user community at large, so that questions like the one Davide asks here do not even need to be asked as the direction is clear.

Perhaps a discussion to continue over a beer at some point soon...

Cheers,

Steve

Re: Qlikview vs Qliksense - segmentation or replacement?

robinrouleur — Mon, 06 Aug 2018 00:37:26 GMT

Hi Henric

That is fantastic to hear! Can you tell me if you have show/hide sheet object (based on expression) or bar offset (e.g. for use in your Gant example) on your road map for availability soon? We are very keen to move to Sense but these are road blocks, particularly the show/hide functionality.

Regards

Robin

Re: Qlikview vs Qliksense - segmentation or replacement?

hic — Tue, 21 Aug 2018 09:27:57 GMT

An object show/hide functionality like we have in QlikView wouldn't work well with the responsive design that we use in Qlik Sense. So, I am skeptical to having a QlikView-like solution.

We are however looking at creating a container object that could solve that business problem. The container would then have some logic (defined by the app developer) that defines which of the sub-graphs to show. And this way the container would follow the responsive design logic, while internally having a conditional show/hide of its internal charts.

HIC