What needs improvement with QlikView?

QlikView lacks self-service capabilities, which means users depend on the IT team to make changes. Qlik Sense offers a more modern approach with self-service features, allowing users to build dashboards independently.

Creating an out-of-the-box solution for modeling capabilities might be beneficial.

The product's visual capabilities could be improved. The graphs and visualizations are not as aesthetic or easy to create.

Many of the features in Qlik Sense need to be available and reintroduced in QlikView. I believe many of the features have been added to QlikView after the layout containers were introduced. QlikView used to be a way more customizable tool than Qlik Sense is in the present time. Improvements are required in the hide and unhide functionality that falls under the layout container feature that has been used in my company in recent times. Hiding off the apps in the app overview tab based on the access was a really good feature that needs to be introduced back in the product since I see that, at the moment, there are multiple groups on the tool, owing to which multiple changes on the QMC part is required to handle the solution. Only the person with access to the dashboard in QlikView could have a link to the dashboard through QlikView's hub or access points. With Qlik Sense, one can see whatever is available in the stream. If a user wants to control everything in the product, then there is no need to make multiple changes in the QMC at the individual app level. The aforementioned area can be considered to improve Qlik Sense.

QlikView's UI could be more user-friendly. At present, I encounter difficulties while writing complex queries on the UI. It doesn't support the query button as well.

The tool is expensive in Turkey.

There is room for improvement in terms of scalability. Because it depends on the use case and customer requirements. If QlikView can't handle the scale, I usually look to the data lake or data warehouse for solutions. My experience is that for self-service BI, users often request low code tools, which wouldn't be suitable for the QlikView front-end due to performance limitations.

QlikView certainly lacks in its ability to share visualizations or create visualizations easily. QlikView is a powerful tool but has shortcomings when compared to the visualization capability provided by Qlik Sense or Power BI. From my perspective, I understand that since QlikView is an older product, it can be simply left as it is, and users can move to Qlik Sense, which provides a much stronger visualization. If QlikView decides that its visualization part should be just like Qlik Sense or Power BI, then I would say it would be too much to capture in one or two phrases, considering that it is overall much easier to create visually good-looking dashboards and also something like a geographical map which is not possible in to get in QlikView currently.

They should offer the capability to directly access data from SaaS environments, as it would simplify the migration process, and while it may seem like a minor enhancement, it would be beneficial to our clients. Some clients have requested a hybrid environment where both QlikView and Qlik Sense can work together effectively during the initial stages of migration, so that would be a good feature to add.

There is a challenge on the frontend when it comes to browsing data through QlikView, as it isn't entirely compatible with other platforms we use.

I'm not like a lot of people who are into AI, especially when it comes to making queries. I don't really remember if QlikView has this feature, the one where you write up a question about the data in human language, and they just bring up a quick analysis from it. I'm not sure if this feature exists. But if it doesn't, it should be something they consider adding. I believe assisting users with quick building using natural language queries is not as simple as just making a regular query. I like the idea of using human language queries. That would be a plus, really. QlikView should improve the integration with scripting. It has its own scripting language for building the underlying data layer. Sometimes, dealing with complex reports requires more effort, and that could be really improved.

There are a couple of things right now to consider since QlikView is going to be out of the market. Instead, Qlik Sense will be the new platform. Right now, QlikView is switching up. So there are some enhancements in Qlik Sense required. Though the initial setup phase is simple, when it comes to the integration with the custom systems, the configuration and the compatibility sometimes take some more time. The aforementioned area can be considered as room for improvement.

It is really old. We are moving towards converting everything into a Power BI environment. We want to have a self-service type of BI environment where different levels of users in organizations can log onto a portal and retrieve the data they need or get the necessary insights for decision-making that's important for them or their business unit. They have built a new version of QlikView called QlikSense, which probably competes with newer BI tools, such as Power BI, but they are far behind. That's why we are moving towards a newer tool that's easier to use and has more visualizations to represent the data. QlikView is very old, and there are more modern tools that work. It is expensive. Its licensing can be improved because the tool is old. If they still want people to use it a lot, they should substitute it for a newer, better BI tool. The price should change for what you get. They can have a cloud version for it, but I guess they have created QlikSense to have a cloud version or platform available so that people basically go from QlikView to QlikSense. There is a learning curve. It is not for first-time users working with data. It has got its own little syntax to create usable datasets, codes, schedules, etc. So, there is quite a learning curve to learn the syntax to use the tool, but if you build expertise in it, it is nice to use.

It works properly most of the time. I can't speak of any areas that need improvement in terms of features. It would be ideal if it was a little bit faster. They could improve the speed. It's not slow per se, however, sometimes it just takes some time to give you the results you want.

The user interface of QlikView is old. The provider built a new tool called Qlik Sense. So Qlik Sense is basically the offspring of QlikView. Somehow both are still supported and they've developed new versions for both of these tools but Qlik Sense is basically the restyled version of QlikView. There's a lot of discussion about some features which are difficult to use including the user interface, all look and feel aspects, but I think that will be in the new version. What they could provide is a migration path to Qlik Sense. It's very difficult to do that automatically because it always requires you to check and change some new port. I haven't researched it but I believe that's the case.

We find Tableau to be a bit of a better solution. QlikView should try to be more like that. The solution is quite costly.

QlikView lacks the development aspects that its sister product QlikSense has got. It would be nice to also get the new graphs that are available in QlikSense in QlikView. It would be nice if QlikView could be plugged in into the company's website or an online portal such as QlikSense is capable of. There are ways around but it takes enormous time to develop. Certain features such as a cumulative result, as is possible in QlikSense, would be nice to have since it takes quite some time to get this right from a developer's point of view.

The performance can be improved. There is no automation or drag and drop functionality.

I really wish the application was easier to use in the development phase. Our business model relies on the business to build their own reports and many departments did not have the associates they need with this type of skill set (i.e. SQL experience). In a business model where a centralized department (i.e. IT) is in control of the reports for the entire company, this would not be a problem. The development was the ultimate reason this application did not take off in my organization vs. a competitor's application (Tableau). This is a shame as the finished dashboard appeared to be more polished.

This solution would be improved with the inclusion of a feature that would allow us to add a common library of (our) commands used in load scripts and expressions, so with a keyword, we would get a drop down to select the command we are looking for, as opposed to the generic help. I keep them all in OneNote now and copy and paste them in, then change the field names. This addition would really save time. examples: Convert date-time stamp to just a normal date in the Load script - so we can match to the company calendar for Model Year / month etc , Fiscal Year /month / week of year/ week in year date(floor(DTTMSTAMP),'MM/DD/YYYY') as TransactionDate, Storing QVD's: (this is the path needed from a Data Loader) STORE SummarySalesAggregate INTO [..\QVDData\SummarySalesUnitsAndDollars.qvd]; Sorted and Count for creating Arrays: SortedAndCounted: Left join (SummarizeSales2) LOAD Option_Inv, Line_No, if(peek('Option_Inv',-1)<> Option_Inv,1, Peek('counter',-1)+1) as counter Resident SummarizeSales2 Order by Option_Inv asc, Line_No asc;

* Improvement in the graphical user interface * Introducing HTML 5 * Context sensitive * Drag and drop visualization * Responsive design.

I would want them to have more options as a user. It would be nice for them to create their own dashboards and add fields.

Tools that can be improved are: * Visualization charts * Pricing * UI transparency

More/newer visualisation components need to be added. QlikView's ability to embed custom visualisation is not a great experience.