Qlik announced that the two products were there to fulfil two very different purposes the Guided Analytics of QlikView and the true Self Service BI of Sense.Īs a long-time QlikView developer (who has crafted many an application that guides users to discovery through designing a UI to encourage this) I can see that distinction clearly. Was QlikView being replaced by Sense? Why would you want the old when you can have the new? In a previous blog post I likened them to siblings: most parents would find it hard to admit they have a favourite child. With the release of Qlik Sense there appeared to be a bit of an identity / branding challenge for Qlik. This adds a further dimension to the Qlik Sense / QlikView debate. I have written a subsequent post that follows on to this one, relating to the opportunities presented by interacting with the API in Qlik Sense: Qlik Sense APIs, Mash-Ups and Lego. It seems only appropriate therefore to create a blog post that references both.

There is something tactile about Lego and the simple act of snapping two pieces together, and having them fit together perfectly, is a joy.īoth Lego and Qlik have improved my life and can do the same for others. As a child of the 80’s it played a big part in my childhood and now as a father of two it is great to see my children getting the same enjoyment from it. You probably are not aware however that I also love Lego.

If you read this blog regularly you will know that I am a massive fan of QlikView, and am very excited about the future of Qlik Sense. There may not seem to be a direct connection between these products, but Qlik’s new two-product strategy has got me thinking: perhaps they are more alike than you might think.

Qlikview latest version 2017