1) Qlik Sense being recently launched and a hot topic in BI space with rich Visualization and being introduced as a self service BI. Talks are going on that excel users could be the best potential target for Qlik Sense. Can anyone comment on it? To my knowledge Macro is not supported in Qlik Sense and having limited aggregate functions such as SUM, AVG, COUNT etc. so how can we convince the excel users to adopt Qlik Sense? To me they will not be able to replicate their excel sheets to Qlik Sense, if there is macro.
2) Does Qlik Sense necessitates a data warehouse at the back-end? To me yes, else how is that going to be a BI tool. Can anyone throw some light on it ?
3) Can Qlik Sense be proposed to a prospective customer who is cost conscious and not opting QlikView as it is Costly ?
4) However Qlik Sense server is more sophisticated as compared to QlikView in terms of Architecture,governance, security , Deployment etc. which they claim much better than QlikView and all major issues of QlikView has been addressed in QlikSense Server. so not sure what is their future road map, it is bit confusing to me. Ideology of both Products contradicts each other.
Any experts who is in PreSales can throw some light on it?
You have asked a lot of questions here but I will try to give you some useful information. Most importantly, if you are experienced in using QlikView then it is worth downloading the Qlik Sense desktop and spending some time with it to understand the major differences. Words can only go so far.
1. Qlik Sense is not trying to be a replacement for Excel in terms of spreadsheets and macros. It is however very good at taking data from Excel and creating excellent visualisations. Almost all of the functions from QlikView can be found in Qlik Sense, not just SUM, AVG, MIN, MAX etc. There is also an excellent set of APIs and being based on web standards make many types of integration and extension possible.
2. Just as with QlikView, Qlik Sense can work with or without a data warehouse. The load scripts and capabilities are very similar between the two.
3. Instead of worrying about the cost you need to be looking at the value that each product can bring and the user cases to be solved. Once these are understood the correct solution can be proposed. Cost should not be the main driver of the decision.
4. Qlik Sense and QlikView fulfill the needs of different parts of the BI spectrum. QlikView is very much aimed at guided analytics, helping users explore the data and answer their own questions but in a controlled way. Qlik Sense is much more about the ability too freely explore your data, create new visualisations and share new insights through storytelling. There is an updated QIX engine to make it more efficient and the architecture and governance capabilities have been hugely updated.
There are a lot of resources explaining the new capabilities of Qlik Sense, such as the Qlik YouTube channel and all of the materials published in this community, but getting your hands on is really the best way forwards.
. Talks are going on that excel users could be the best potential target for Qlik Sense.
Maybe not until QS has a built in PT
IMO QV would be better for advanced excel users
If we get the chance to migrate to Qlik Sense the first users will be in our Finance department.
At the moment some users especially in Finance just use Qlikview to get data into Excel if they need to
do more analysis. Qlik Sense might prevent this from happening.
The other issue we have here is presenting QlikView\Qlik Sense as an alternative to the Oracle Essbase system that Finance users have access to.
Why is this an issue re dumping into Excel. I do it a lot when required
And have you tried setting up adhoc reports for the finance users.
I'm a big fan of excel but can get most of my reports from QV
have you shown finance users how to set their own reports /apps up in QV
Out of interest why is finance using oracle for reporting an issue? I'm happy for users to use whatever they want as long as the information is accurate etc. QV is being installed because the quality of the reports is so much better. But finance usually already have good reports already set up
'Why is this an issue re dumping into Excel.'
The problem is not with just exporting to Excel which is fine for emailing.
The real problem is when users perform a lot of analysis in Excel then want a change to the data they have extracted from QlikView so they have to spend a lot of time updating all their spreadsheets.
When it would have been better to have the analysis all done in QlikView\Qlik Sense where changes to the data model \ objects would not require alot of manual updating in Excel.
'have you shown finance users how to set their own reports /apps up in QV'
Users have been shown how to create their own charts\tables\lists but most only go as far as creating listboxes without help.
'Out of interest why is finance using oracle for reporting an issue?'
The only problem I have with Oracle is that it might kill off Qlik within the company.
We have seen an interesting shift here where people who never touched QlikView are suddenly having a lot of success making their own visualisations with Qlik Sense. The improvements in user experience for non-designers has had a big impact on what people feel able to tackle.There are still the nay-sayers who won't try but they are being left behind.
When people are developing their own visualisation apps it is sparking off more conversations about how to show the data and what it means. It is far more dynamic than Excel or QlikView.
Thanks for the reply
I found QV easy to set up new straight and Pivot tables but not so easy with the graphical charts. So QS may be the future ...
Apart from the fact that in the Qlik Sense Desktop (1.1.0) pivot table you can't export to Excel at the moment.