34 Replies Latest reply: Mar 3, 2017 3:34 PM by Daniel Greenberg RSS

    Can someone explain the difference between Qlik Sense and QlikView?

    Chetann Sehgal

      I do not understand why this tool was launched in parallel to QlikView in the name Self BI.

        • Re: Sense....Worst BI tool ever developed
          Robert Mika

          Actually, Sense won couple of Awards:

          ttp://www.qlik.com/us/company/awards

           

          If you moving from View to Sense is hard to understand why...

          If you new to BI you are pleased that your users/employees have the ability to create analytics without very large knowledge.

          Is SelfBI as is using drag and drop approach to interact with data.

           

          Pure Desktop applications become outdated that's why Sense comes into play...

            • Re: Sense....Worst BI tool ever developed
              Chetann Sehgal

              Thanks Sir.

              I am a follower of Qlik and QlikView and working on QlikView for past 5 years. I enjoyed  working in QlikView and found it most advanced, robust BI tool as compared to other BI and tools.

               

              But sorry to say sir, working in Sense is very annoying for a developer who  has worked in QlikView before. It is entirely based on extensions and lacks of numerous number of features.

              Qlik is promising that it will incorporate the features in coming years but those features but i think it would be hard to incorporate those as it is Display size independent tool.

               

              I have heard that QlikView is going to be decommissioned after some time.

               

              Request you to please correct if i am wrong.

                • Re: Sense....Worst BI tool ever developed
                  Robert Mika

                  Sense needs different set of skills (HTML,JS, CSS)

                  and you can achieve similar results that in QV.

                  Is the choice Qlik took if you like or not.

                  QlikView will be still supported for some time.

                  • Re: Sense....Worst BI tool ever developed
                    Zhihong He

                    Hi,

                    I am surprised to see the discussion that Qlikview will be replaced by Sense.

                    In my mind, I thought QV will exist parallel with QS. And my next plan for the BI solution is to use QV for develop and internal usage, and QS for external, like for clients, and for internal usage of simple analytics usage.


                    And if one day QS  can really be developed as convenient as QV, then I do not mind to totally move to QS, but I believe it will still take a little bit long time.


                    Zhihong

                    • Re: Sense....Worst BI tool ever developed
                      Aehman K

                      As a Developer I totally understand the frustration. But I hope with each release they will fix those issues which will be helpful for Developers and hope we'll not depend on extensions totally. Surprisingly we do not have big issues in Qlik Sense but only UI related issues (coloring, labeling, sorting etc...)

                      Qlikview v12 Vs Qlik Sense 3.1

                      They getting there..... but again the users are quite happy because they only know UI part and Sense has Self serve option. One of the biggest reasons it is good for users and for developers it is hard way to learn.

                      • Re: Sense....Worst BI tool ever developed
                        Vladimir Komarov

                        Chetann,

                         

                        As you've mentioned, you've been working with QlikView for 5 years, so you've started around the time when QV v.10 was released, correct? So, QV was pretty mature product back then....

                         

                        QS was released just three years ago and (of course) is going through "growing up" issues right now...

                        Yes, a lot of things in QS are not working the same way as in QV, but there are several features in QS that simply impossible in QV (automatic screen resolution adjustment, auto data refresh after reload, extensions flexibility, etc)

                         

                        Yes, QS extensions' development require more (and different) skills, but the possibility and flexibility are endless!

                        I think Qlik have selected completely right approach with QS (using open architecture and APIs) so they will be very successful with this new product. 

                        And do not worry, they will keep QV on the market for a while, but I would strongly suggest about start migrating to QS at some point in the near future....

                         

                        VK

                          • Re: Qlik Sense needs more and more improvement...
                            Chetann Sehgal

                            Thanks Vladimir,

                             

                            I agree with your point that it will take time to reach that level, but my point is QlikView should not be decommissioned as it also very flexible tool.

                            The only demerit of View is that i cant adjust according to the screen size. It also provided self BI at the access point level. A business user can create custom dashboards dynamically.Sense on other side requires expertise in JS,CSS,HTML.

                             

                            It would be great if both the tools exist in parallel in coming future as well.

                            QlikView :       For Guided Analytics for middle level management (Complex and Advanced Dashboards)

                            Qlik Sense:     For Dashboards at CXO level (Basic Dashboards)

                             

                             

                            Thanks,

                            Chetan

                              • Re: Qlik Sense needs more and more improvement...
                                Vladimir Komarov

                                I am not sure why you think Qlik will decommission QV...

                                As far as I know, QV v. 13 will be released next year. Qlik is not planning to add a lot of new features to QV, but they will be releasing bug fixes and "modifications" for several more years.

                                 

                                And will support existing versions for few more years after that... 

                                 

                                It's obvious that QS is being pushed as a main platform, but QS and QV is sharing an engine now, so it will not be very difficult to support both systems in parallel for a while, IMHO.

                                 

                                VK

                                • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                  Vladimir Komarov

                                  Chetann,

                                   

                                  One more note: I do not agree with your "Sense on other side requires expertise in JS,CSS,HTML" statement...

                                  These skills are required if you are developing Qlik Extensions. You might need to know few basic rules if you are utilizing Mashups too (but there are several Qlik Dev tools that help you with that already), but you do NOT need these skills to develop Scripts, Data Models, and regular UI items. It's about 95% of the total effort.....

                                   

                                  There are other people who know how to do the JS/CSS/HTML stuff and they are sharing their components with the rest of the world:

                                  1. Qlik Branch

                                  2. QlikMarket

                                   

                                  I am not an expert in Web-development, I just know few good people who can do pretty much anything in that area

                                   

                                  VK

                                    • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                      Chetann Sehgal

                                      Thanks Vladimir,

                                       

                                      Yes there are many benefits of using Sense but during development phase, the small small issues act as hurdle in achieving a result for a requirement.It either needs an extension(which sometimes dont help)  or Mashups(which cant be used everywhere).A very small example would be adding manual colors to a Combo Chart , i might need to create an extension to achieve this, as i have tried different methods for the same.

                                       

                                      Also the concept of

                                      Layers,

                                      Object Overlapping,

                                      Hiding/Un-hiding Objects

                                      Create Reusable Themes

                                      Changing backgrounds of the sheets and Objects

                                      Copying/Pasting Multiple objects as same time took was game of a second.

                                      and many more.

                                       

                                      These features may look small but are very helpful in serving complex to complex requirements made it very flexible.


                                      Sense on the other hand is screen size independent ,so the above features might not be incorporated in coming versions.

                                       

                                      Thanks,

                                      Chetan

                                        • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                          Vladimir Komarov

                                          Nice list of necessary improvements, Chetann!

                                           

                                          I would add few more:

                                          1. Saving entire script to a TXT file

                                          2. Adjustable grid (or smaller cells, at least)

                                          3. Functions in tables' labels/headers

                                          4. Containers ...

                                           

                                          Some of them are really complicated to implement on the new platform (and Qlik, unfortunately, has a habit to de-prioritize features that don't benefit end-users directly) so I doubt that they will be implemented any time soon...

                                           

                                          But I know that "Changing backgrounds of the sheets" is already available directly in QS...

                                           

                                          VK

                              • Re: Sense....Worst BI tool ever developed
                                Guruprem Saginadham

                                Dear Chetann, Please change the post title, it is hurting me.

                                • Re: Sense....Worst BI tool ever developed
                                  JULIAN RODRIGUEZ

                                  It sounds like an passionate title,


                                  Take a look to the world's largest survey and what it says about Qlik Sense.

                                   

                                  http://www.qlik.com/us/resource-library/barc-bi-survey-16

                                   

                                  And then, think twice if it's really the worst BI tool...

                                  • Re: Qlik Sense needs more and more improvement...
                                    Michael Tarallo

                                    Hello Chetann, et all - thanks for all your support of Qlik Sense and thanks for seeing the value it provides.

                                     

                                    Chetann - I was recently interviewed for someone's blog and there was a question that you will be interested in related to your concern and question - I will provide it here:

                                     

                                    Q: Can Qlik Sense do everything that QlikView can? How?

                                     

                                    Mike Tarallo: We get this question a lot. Short answer is Yes and No.  First it is important to note that QlikView and Qlik Sense use the same exact powerful engine. So both products are benefiting from the speed and performance of the QIX indexing associative engine, that which makes Qlik unique. The power of green, white and gray – the associative experience is still a huge part of Qlik’s products, and it is this capability that helps organizations find the unexpected, ask the next question and see the whole story that lives within their data…..But, the way you designe a specific user interface or user interaction in QlikView, has evolved and therefore there may be a better way to achieve the same or similar functionality in Qlik Sense, OR perhaps what you designed in QlikView may not make much sense in Qlik Sense, ( i.e. Layering which does not existing in Qlik Sense due to its mobile ready responsive design and adaptive grid. ) QlikView has more of a develop / publish / consume model where you can make very specific dashboards and user interactions and provide multiple layers.  Qlik Sense – while it can certainly cater to the develop / publish / consume model – also allows for self-service and embedded uses cases. It has a more streamlined user interface and richer API layer built on open standards.

                                     

                                    We built Qlik Sense to leverage popular open standard developmental specifications and developmental syntax. JSON, CSS3, HTML5 and JavaScript to be exact. These are very common within the web world when developing apps. Basically, anyone who knows how to develop web apps using these can work with our robust set of APIs to create basically anything they can think of. We have an Engine API that allows you to interact with data at all levels. You can develop your own front-end client interface the way you want and leverage the benefits of our indexing engine (QIX). We also have what we call our Capability APIs which allow developers to easily embed Qlik content into their own web applications with just a few lines of code. These APIs consist of the Root API, App API, Visualization API, Selection API.  You can also simply call a Qlik Sense APP URL into an iframe and embed it into a CRM like Salesforce. I believe the simple answer here is … you have many choices of how you wish to deploy Qlik Sense and you are limited by your imagination, not the software. Don’t believe me? Check out our developer exchange network Qlik branch http://branch.qlik.com/#!/ and its sister site the Qlik Playground: http://branch.qlik.com/#!/blog/57e297eb34193fe96af041a0 - you will see some amazing “things” created by those with a thirst for making their dreams become reality.

                                     

                                    Due note that we recognize there are certain capabilities in QlikView that would also make sense in Qlik Sense and we do take that into consideration and add these features accordingly. While making sure said features do not interfere with the ease of use that Qlik Sense users have already come to love. So, 4+ years ago we started a project,  QlikView.Next. We asked ourselves “How would we build the next generation of QlikView software?” Using today’s modern technology and open standards, Qlik Sense became that next generation product, therefore becoming a new product with most of the goodness of QlikView. QlikView allows me to feel really cool and powerful because I can make QlikView bend to my will, however that does not necessarily mean what I can create as a developer may necessarily benefit the user. If you need to be all that powerful and have so much control with Qlik Sense, there is a much better and modern way to do that using Web Mash-ups, APIs and open standards such as HTML, CSS, JavaScript and JSON.

                                     

                                    Q: Is the QlikView product coming to an end?

                                     

                                    Mike Tarallo: No. To put it simply, we delivered QlikView 12 in December, 2015, pretty much fulfilling our commitment to our continued investment in our proven, market-leading data discovery solution. QlikView 12 includes a number of enhancements including the next generation QIX engine, that is compatible with the Qlik Sense engine, as well as additional performance improvements. QlikView will also benefit from our planned investments in Qlik DataMarket and Qlik NPrinting. We plan to support and deliver SRs on QlikView 12 for a period of 24 months after the next major release of QlikView, or longer at our discretion. Support for QlikView 11.2 will be provided, for a period of 24 months following the release of QlikView 12, or longer at our discretion. Please note that Qlik‘s strategy and possible future developments are subject to change and may be changed by Qlik at any time for any reason without notice, and Qlik makes no commitment that any future functionality may be available as part of software maintenance. The foregoing information should not be relied on in making a purchase decision, and may not be copied, distributed, or otherwise shared with any third party. We plan on releasing another version of QlikView 12 later this year. Remember, QlikView is our flagship, industry proven product. It is a mature product with a huge feature set, going forward with future releases we are investing in performance, scalability and stability.

                                     

                                    Q: How are companies dealing with the Qlik Sense, do they continue to create dashboards and guided analysis or is self-service BI becoming something real?

                                     

                                    Mike Tarallo: This is a great question. First let me state that self-service always existed it just did not have a “label” on it and came in different forms. Whether it was using MS Office products, an off-the-shelf, packaged application, or a home-grown app – companies were always looking for better and faster ways to have business users get the information they need with little to no involvement from IT or others. Problem was, these apps offered to much or too little in the means of functionality and usually always required some sort of setup or involvement from technical staff. Whether it was getting the parameters to connect to the right data source, writing a SQL query statement, or creating a semantic layer – someone else had to help and that really isn’t the definition of self-service. Once those hurdles were overcome you still had multiple versions of the truth, spreadsheet chaos and lack of confidence in the data therefore delaying decisions. In many cases, there are still those companies that take the results of their BI system and have IT specialists execute SQL queries against the raw data to make sure the numbers reconcile. Organizations should be debating over the decisions and not where the data came from or if the numbers are correct. Many also use the BI tools to export the data into Excel and then use Excel to calculate and create reports. Exasperating the initial problem of creating multiple versions of the truth.  Is that really a smart way to leverage your investment in BI? No it’s not. With Qlik Sense – it provides true self-service analytics prepared from governed libraries all from within the same interface, without the need for cumbersome semantic layers, complex data models, or SQL queries.

                                     

                                    In regards to what is being created, this answer will vary depending on the companys’ needs and use cases. Some are using both QlikView and Qlik Sense as they both can complement one another by taking advantage of existing skill sets in the organization. Some companies are migrating all QlikView applications over to Qlik Sense. Some companies are maintaining their QlikView applications but are developing only new applications with Qlik Sense.  It is somewhat related to the first question as Qlik Sense can be used to support a variety of customer use cases. Qlik Sense out-of-the-box is excellent for Self-service data preparation and visualization as well as guided applications, this of course depends on how one defines the user that will be consuming the application. Anyone can get started quickly. You can create dashboards in minuets as I show in this video: https://www.youtube.com/watch?v=MARjUr2dZRs – but where Qlik Sense also shines is when it is used for other use cases like guided, embedded and custom analytics. We built Qlik Sense to leverage popular open standard developmental specifications and developmental syntax. JSON, CSS3, HTML5 and JavaScript to be exact. These are very common within the web world when developing apps. Basically, anyone who knows how to develop web apps using these can work with our robust set of APIs to create basically anything they can think of. We have an Engine API that allows you to interact with data at all levels. You can develop your own front-end client interface the way you want and leverage the benefits of our indexing engine (QIX). We also have what we call our Capability APIs which allow developers to easily embed Qlik content into their own web applications with just a few lines of code. These APIs consist of the Root API, App API, Visualization API, Selection API.  You can also simply call a Qlik Sense APP URL into an iframe and embed it into a CRM like Salesforce. I believe the simple answer here is … you have many choices of how you wish to deploy Qlik Sense and you are limited by your imagination, not the software. Don’t believe me? Check out our developer exchange network Qlik branch http://branch.qlik.com/#!/ and its sister site the Qlik Playground: http://branch.qlik.com/#!/blog/57e297eb34193fe96af041a0 - you will see some amazing “things” created by those with a thirst for making their dreams become reality.

                                     

                                     

                                    Hope this information is useful to you.

                                     

                                    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.

                                     

                                    Regards,

                                     

                                    Mike Tarallo

                                    Qlik

                                    • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                      Robert Hutchings

                                      Ive asked users what they prefer. View or Sense. (when Sense was still version 1)

                                       

                                      Sense won hands down. Ok it was a fairly small sample size but it was such an easy win for Sense that I dropped View and moved to Sense. Even View users when shown a converted App said Sense was better

                                       

                                      Moving from View to Sense was a joy. Moving back to View for one contract after just using Sense for 6 months wasn't. But if developers want to stay with View fair enough. But I think they are doing new users a disservice unless there is a very good reason to buy View instead.

                                       

                                      The reason I prefer Sense is as follows. (I'm always happy to show users both. Pointing out the pro's and cons of each. When I do so far Sense has always been an easy winner -but not a huge sample size. I have also converted enthusiastic View users to Sense after showing them the difference.)

                                       

                                      1          Best View features retained

                                      2          Updating and developing Apps on the Server

                                      3          A more Modern Product

                                      4          Easier to Use especially for less skilled technology users.

                                      5          Users like the ease of use of the Sense Pivot Table.

                                      6          Screen adapts to screen sizes and form factors.

                                      7          Easy automatic script writing option for simple loads (bubbles).

                                      8          Story Telling

                                      9          Self Service

                                      10       Re-useable Master Items

                                      11       Set up Visualizations and Sheets more quickly

                                      12       Easier to set up professional looking sheets

                                      13       Better looking more modern Graphical Visualizations

                                      14       Personal Edition. Can share Apps

                                      15       Free Cloud with 5 options to share


                                      There are a few features missing in Sense. Like triggers. I would also like to see more color options, an adjustable column width for the pivot table, drill around for tables etc. but for me these are minor things that will be done in time

                                      • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                        Chetann Sehgal

                                        Thanks everyone for your inputs. I would really like work on both the tools as i really love the concept behind it and engine behind qlik tools which makes it robust tool and separates its from other BI tools.

                                         

                                        I hope small things will soon be incorporated in the Sense as default features because customizing the extensions needs time and additional cost for the clients.

                                         

                                        Regards,

                                        Chetan

                                        • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                          Luis Garcia

                                          From my point of view all depends the kind of project you should to make. QlikView is really recommendable for medium and big project with a heavey stable dashboard and QlikSense is recommendable for clients who has technology skills for light queries

                                          • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                            Arnaldo Sandoval

                                            I want to add one more thing for those concerned about Qlik Sense and View; Qlik Sense is indeed friendly and end-users can really get the answers hidden in the business data, but our end-users are not IT professionals, getting the data, building the data model for Qlik Sense applications, still require developing the scripts, if the source data is not complex, some end-users will be able to help themselves, which is always a win-win scenario for any Business.

                                             

                                            Now building Data Models in Qlik -either one- has its challenges, synthetic keys, circular references, data quality, duplicated records, dealing with dimensions, data security rules, etc, some end-users will face strong difficulties with these challenges and this will become the role for the IT team, assist end-users gathering the data needed.

                                             

                                            It is not the end of the world, and Qlik, as a company is very aware of the challenges ahead, 1 year from now Qlik Sense will incorporate features currently present in Qlik View only, I am enjoying how Qlik Sense is growing up.

                                              • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                Michael Tarallo

                                                Nice! - Thanks for the great input everyone!

                                                 

                                                 

                                                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.

                                                 

                                                Regards,

                                                 

                                                Mike Tarallo

                                                Qlik

                                              • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                Michael Tarallo

                                                Hello All - some more information regarding QlikView that you might be interested in:

                                                 

                                                QlikView 12.1 – Top Secret Plan Revealed | Qlik

                                                • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                  beck bakytbek

                                                  Hi Sehgal,

                                                   

                                                  with a few words:

                                                  -QlikVies has Macros

                                                  -QlikSense: Here you should use extension (instead of macros)

                                                  -QlikView: more granular then QlikSene

                                                  -QlikView: If you create your own app, nobody is able to see it, you can not share it with other colleaegus

                                                  -QlikSense: Here you can share your app with other

                                                   

                                                  and look at this: What is difference between Qlik Sense & QV Desktop client?

                                                   

                                                  beck

                                                  • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                    Daniel Greenberg

                                                    In my opinion which I know is shared by others QlikView is the choice for guided analytics and Qlik Sense can be better for self service BI but it depends.

                                                     

                                                    Qlik Sense does not make nearly as good use of real estate as QlikView and you cannot fit as much on the screen.


                                                    We also have a QlikView dashboard with a highly customized report builder that also allows users to add their own chart and I would say this is easier than doing it in Sense.

                                                     

                                                    Sense is great but it is not the be all end all and QlikView is often still the correct answer but it depends

                                                      • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                        Robert Hutchings

                                                        "We also have a QlikView dashboard with a highly customized report builder that also allows users to add their own chart and I would say this is easier than doing it in Sense."

                                                         

                                                        Hi Dan

                                                         

                                                        Could you expand on this please? As Sense has master items and the charts are very easy to add as required in Sense. Much easier than View. Also I prefer the ease of setting up a customizable straight table using the Sense climber extension than how its done in View. It takes a long time to get this all set up in View but easy in Sense.

                                                         

                                                        "QlikView is the choice for guided analytics and Qlik Sense can be better for self service BI but it depends."

                                                         

                                                        Agree with it depends. I can't really see much difference regarding guided analytics. Both Sense and View are fine. Although maybe triggers make View better in this respect but Sense is easier to use so it can almost cancel out.

                                                          • Re: Can someone explain the difference between Qlik Sense and QlikView?
                                                            Daniel Greenberg

                                                            rb1.png

                                                            In QlikView we have a hierarchical list box with fields that can be added by category to our Report Builder. 

                                                            I have yet to find a way to do something this easy for the end users in Sense.  Keep in mind I am talking straight out of the box functionality not extensions.

                                                             

                                                            Also when talking about a report builder at least in our cases the users want many many columns.  I am not Sense bashing I really do like product but in comparison to QlikView it has poor use of real estate.  Since our users want to pick many columns to add to the tabular report and QlikView shows so much more on the screen QlikView is better for this IMHO. 

                                                             

                                                            Additionally if we develop for our standard 24" Monitor and someone uses it on their laptop they will have to scroll in QlikView to see more columns, not the end of the world.  In Sense you will have to (not sure what it's called so forgive wrong vernacular but you will have to toggle which columns are enabled so you can see the ones that are important to you.  Perhaps I am overlooking something obvious in Sense here because I don't have the experience in Sense I do in QlikView but that's kind of a pain to me.

                                                             

                                                            I know a good dashboard shouldn't have tons and tons of columns and I have been preaching that for years but sometimes the users just need that.