Some of the most common questions we hear from Qlik users is when and why should I switch from QlikView to Qlik Sense. If your need fits one of these three reasons, you may want to consider switching. But don't worry, we've got pro tips to help you have a smooth transition.
Two of the most common questions we got from Qlik users stopping by our booth at Qonnections this year were:
Let’s tackle both of these questions.
There was a lot of buzz around Qlik Sense 3.0 at Qonnections. And for good reason.
Qlik Sense 3.0 includes some highly anticipated functionality such as, on-demand app generation, data market expansion, super easy visual data prep, and the integration of QV Source (more on Qlik Sense 3.0 need to knows here). So naturally, there were many people inquiring about if they should switch to Qlik Sense.
The reasons why a lot of our clients make the move to Qlik Sense from QlikView or why they add a Qlik Sense environment to their QlikView environment are:
A little disclaimer: Before you decide to switch from QlikView to Qlik Sense, you first need to consider what you are trying to do with your data:
There are many reasons to use either product (or both) depending on your use case, so consider your business reasons for using the technology first.
Moving an app from QlikView to Qlik Sense is pretty straightforward. Just drag your QlikView app (.QVW file extension) and drop it into your Qlik Sense Desktop environment. For more details on this process, one of our consultants explains the step-by-step process here.
While the process for moving your apps from View to Sense is fairly easy, there are a few things to be aware of as you are building apps in Sense:
The best practices are slightly different in the two products and you should think about these as you are developing in Sense. For example, when working in Sense it’s a good idea to take advantage of Master Items.
Master Items are dimensions and measures that you can create, save, and reuse. A good practice is to define your measures and dimensions of your app up front and create master items that you can reuse to create visualizations.
There are many more best practices for Sense from Qlik users on the Qlik community.
Although front-end objects in QlikView do not automatically transfer over to Qlik Sense, most users find the simplified design in Sense a welcome change that works on most devices out of the box and also offers some very useful functionalities for the end-users and can be easier to configure. However, it’s important to recognize the differences in functionality and the user interfaces of QlikView and Qlik Sense.
We cover these topics in more detail in our Qlik Sense 3.0 Webinar that you can Watch On-Demand now. You'll see the newest features of Qlik Sense 3.0 in action and see how you can convert your QlikView apps to Qlik Sense.