QlikView Reviews

The primary use case involves analyzing data on a daily invoice level with QlikView. Building metrics using simple language, similar to what you have in Excel, is what I have found most valuable in QlikView.

Building metrics using simple language, similar to what you have in Excel, is what I have found most valuable in QlikView.

The data model process is acceptable; you can use something simple like SQL in combination with the same metric building language. This combination allows you to perform metrics building on the front-end or back-end depending on your needs. For quick data modeling, you can use it on the front-end and then push it to the back-end with QlikView. QlikView has a good scripting language.

Data integration capabilities are quite good; you can integrate any information stored anywhere in different systems with QlikView.

It is quite possible to work with large data volumes through QlikView, with response times between one to three seconds.

We are not using analytics features and possibly predictive analytics and forecasting features in QlikView, although they are available.

QlikView is very flexible, but we are currently using only tabular presentation of data because that is what we need. Presenting a large volume of data in QlikView with graphics can be overwhelming for the majority of people who want to see a lot of information in one picture.

It would be beneficial to have AI or ML features in QlikView. However, I think they will decommission QlikView, and AI features are already available in Qlik Sense, so you would need to migrate to that platform.

We have been working with QlikView for a few years.

I would rate the stability of QlikView as the best one.

I would rate the scalability of QlikView as pretty scalable. If you want better performance with a larger volume of data, you can simply add an additional server.

I am totally satisfied with technical support from Qlik.

We are still using MicroStrategy solutions. We may have some MicroStrategy Usher licenses, but we are not using it.

We did not have any trouble with the initial setup for QlikView; deploying it was simple.

We went through a local vendor for the purchase process, but he is not dealing with QlikView in terms of supporting us anymore. He was only selling the licenses. Everything else we do internally, and it is a one-man operation.

I would rate the pricing for QlikView as not cheap, but it is reasonable.

I think QlikView is the most advanced of any product. The only comparison we can make is whether we need all the features or if we can move to something already included in our available products. Since we are on Google, why not use Looker? Can Looker really replace QlikView experience? Currently not, but at some point in time, maybe.

I think they implemented a better licensing model in Qlik Sense, where one license can cover multiple reports and applications, making the licensing feature more flexible. I gave this review a rating of ten.

My customers' main use cases for QlikView involve all their data sources, combining them into one, getting a business view primarily in the pharmaceutical industry. They look at sales versus budget, stock at end, making it very commercial and commercial-orientated in my client base, which we use to make commercial and strategic decisions.

My customers are monitoring specific metrics that are all financial, including sales, budgets, and payments.

The best features in QlikView are rapid development, the fact that I can do what I want in QlikView, and full control along with ease of use.

Regarding data integration capabilities in QlikView, they definitely provide a comprehensive perspective to my enterprise metrics.

I am familiar with the advanced analytics feature in QlikView; we do our own mathematical forecasting and statistical forecasting within QlikView, which is all formula-based and expression-based.

QlikView is extremely flexible in terms of visualization tools for communicating complex data insights.

In QlikView, I believe the improvement that should be made is to bring the costs down, as you'll have to be competitive with Power BI, aiming for at least a 30% reduction to stop the hemorrhaging to Power BI, considering that you're losing a lot of customers to Power BI.

Reducing costs is the main improvement needed, as this is the biggest burden currently faced in the South African market, with Microsoft converting QlikView customers due to the perceived cost reduction. I am aware of several big corporations, such as Sanofi and Aspen Pharmacare, which have left QlikView due to cost issues.

I have been working with QlikView for 14 years.

I have no complaints regarding stability in QlikView.

I find QlikView to be extremely scalable.

I deal with QlikView support via a QlikView reseller, and I would rate the customer support a solid 10.

Positive

The setup experience in QlikView is easy and not complex at all, as you can get a tenant set up in Sense within hours, rather than days.

My customers have definitely seen a return on investment with QlikView, as it saves them significant time. For instance, when I take on a new client, they would previously spend endless hours on spreadsheets – doing pivots, analyzing data, and compiling reports – but now all those hours are reduced, allowing them to make strategic decisions and be involved in their businesses instead of wasting time.

A customer would spend six hours a day in Excel, but now they can run their businesses without needing to mess around in spreadsheets. The biggest return on investment is the time saving for the customer.

The license cost per user or per year for QlikView is about 500 Euros annually, and since we are South African-based, that needs to be multiplied.

I have not used the dynamic calculation engine in QlikView as I typically use it for very complicated expressions, so I haven't used that feature.

Regarding additional features, I am a QlikView convert; I have not come across something QlikView can't do, as it can do everything. Even the most complicated things are very doable in QlikView.

To summarize, for those who want to use QlikView, I can have a solution to a customer within one week, regardless of whether I need to use spreadsheets, do ODBC connections to databases, or use any file format such as .dat, .csv, .txt, or old and new Excel. I can connect any database. It is viable, quick, and flexible, and I can provide a solution within days, having done very complicated rollouts within a week, while it would take a month on another platform.

I rate QlikView 10 out of 10.

I use the solution in my company since I like the product a lot. I find it to be better than the other tools in the market.

The tool helps me in the areas of data visualization and business intelligence.

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.

I have been using QlikView for almost a decade. My company has a partnership with Qlik.

Our company did not face any unmanageable stability issues in the product.

My company wants us to embrace Qlik Sense as a whole over QlikView. Qlik Sense as a whole can be considered a scalable product.

I have experience with the product's support team. My company has a large number of users of the product, because of which separate teams get in touch with the tool's support team. If my team has to raise an issue regarding the product, one of our team members communicates with the solution's support team.

A separate team in my company handles the product's configuration and architecture side.

If you correctly use the product for your use cases, it provides value for money.

My firm got the product at a cheap price, but in general, I believe that the product is a bit costly.

Based on where I work presently, the data analytics part of the product is not used much. I look into the data visualization part. A separate team in my company looks into the data analytics part.

Whatever is provided in SOC 1, SOC 2, and SOC 3 of QlikView is good for the visualization part. With the recent releases in QlikView, which happened in November 2023, I can do most of the things that I want with the product.

The product improves our company's ability to find insights in the data.

The product has been integrated into our company's infrastructure, where we also use Alteryx. I haven't explored Alteryx.

The product can be described as a developer's tool. I rate the overall tool a nine out of ten.

We use QlikView for its cost-effectiveness and ease of integration with databases.

The product provides availability or adaptability for building an analytics dashboard. The selection parameters are easy to access. By applying specific filters in Excel, we can distribute a country's sales data into provincial states and then cities. It has efficient breakdown features.

Many types of analysis based on financial or management and accounting concepts require writing expressions. This particular feature could be included in QlikView.

They could provide a user-friendly analysis process rather than specialized IT resource code. Any HR, finance, or supply chain department executive could develop an analysis on the platform.

We have been using QlikView for five years.

I rate the product's stability an eight out of ten.

I rate the product's scalability a four out of ten. We have more than 30 users in our organization. Out of 30, around 50% of members work on processes of different kinds of data selection. The other 50% of the members are part of a team of decision-makers.

We have experience using an in-house management information system (MIS) developed using C++ before considering QlikView.

The initial setup is easy. That is the reason we opted for this product. I rate the process an eight out of ten. We have deployed the product on the server and access it via the web. However, we cannot use it out of the network. It takes 15 to 20 days to complete and requires one person for implementation. Furthermore, it needs two to three developers to develop the product for business. One executive can do the maintenance.

Our sales partner described the process of API integration between databases. A team at our office executed the deployment.

I rate the product's pricing a three out of ten.

I rate the product a six out of ten.

I have a comprehensive use case that involves reviewing various aspects of financial balance, financial planning, accounting movements, and analytics, in addition to other applications related to industrial planning and more.

The key highlight of our work review process lies in the efficiency of data management on the backend. It's incredibly fast and can handle large volumes of data without slowing down our operations. It offers a robust data management model on the backend and a user-friendly data browsing experience.

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 have been working with it for fifteen years.

When comparing QlikView to its competitors like Power BI and others, it stands out for its high stability. I would rate it ten out of ten.

It provides good scalability features, making it suitable for medium to enterprise-level organizations. I would rate it eight out of ten.

They provide technical support for their product but don't offer solution support. The solution support is handled directly by the partners, and I must say, we have excellent solution support as part of our work.

Neutral

Setting up QlikView can vary depending on whether it's in a server environment or a client environment. In a client environment, the process is straightforward and can be easily handled. However, in a server environment, it requires someone with in-depth knowledge of server administration. While the installation itself may not be problematic, the ongoing management can be challenging.

Deployment is a swift process, especially for projects of medium complexity, usually taking around five to ten days. There is typically an additional month for various activities, including engagement with the customer and testing phases, to bring the project to completion.

Its licensing costs are moderate, but it can get expensive due to the numerous add-ons available like those for printing.  Also, there are more substantial expenses when integrating with ERP systems and other solutions. I would rate it six out of ten.

It's an incredibly versatile tool that allows you to handle a wide range of tasks. It's important to note that it may require special attention when dealing with traditional print output and similar functions. I would rate it nine out of ten.

I am working on Qlik Sense and previously worked on QlikView for data visualization and reporting purposes.

It provides a comprehensive data warehouse solution within Qlik Sense, eliminating dependency on external data sources and enhancing data visualization capabilities.

QlikView is an excellent tool, though expensive compared to other BI tools, it provides ETL capability allowing the building of a complete data warehouse within Qlik Sense. It also comes with the associative engine, shared with Qlik Sense, providing excellent performance.

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.

I have used QlikView for four years and Qlik Sense for six years.

Qlik Sense's licensing metrics are flexible. They provide packages based on needs, like named licenses, developer licenses, or shared pool licenses. There is also a core-based license option for organizations with a large number of users.

There are other BI tools like OBI and Power BI.

Qlik Sense is very flexible and recommended for its self-service capabilities in comparison to QlikView.

I'd rate the solution eight out of ten.

We use QlikView for business analytics, primarily for internal insights in the healthcare space.

QlikView employs the Snowflake schema, which becomes an associative model, making it easier to drive insights. Additionally, the intensity with which you can work on the ETLs is quite impressive.

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

I have used QlikView for about a year.

I didn't really face any big challenges with technical support; it depends on the plan. I am not a hundred percent sure.

Neutral

The initial setup is straightforward. I would rate it around a seven out of ten in terms of ease.

Approximately four people were involved in the deployment, though I joined the tool for a short period and am not entirely certain about the current team composition for maintenance.

QlikView is probably on the pricier side than other BI tools. It's more expensive than the overall implementation of Power BI and maybe about or a little less than Tableau. I do not have any specific numbers regarding the cost.

We use other BI tools like Tableau, Power BI, R, and Python.

QlikView's overall product could be enhanced with a bit of finish.

I'd rate the solution seven out of ten.

It's essentially building dashboards for BI. So, the primary use case is back to the reports, particularly dashboards.

One of the good thing is that you can integrate different data source technologies. So you can model your environment without having any of our views running. And I see that our tool would essentially have its own programming language. So that's how you can customize a lot of things.

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.

I have been using this solution for four years. 

It's quite stable. The problems I've faced were mostly related to data issues rather than the solution itself. So I would rate it a nine out of ten in terms of stability.

I haven't encountered issues with scalability personally.

I am satisfied with the support. 

Neutral

I would rate my experience with the initial setup a six out of ten, where one being difficult and ten being easy.

The duration for deployment varies depending on the project's complexity. For some projects, it could take a few weeks, especially when dealing with large reports and multiple dashboards. But there were also cases where it took only a few days.

Usually, there were three or four people involved in the deployment process.

I've worked with Tableau, and they were different at the beginning, Tableau being at an advantage, but now they're very similar. Both QlikView and Tableau have their strengths and weaknesses. Tableau was a bit easier for creating storytelling, but I don't have any issues with QlikView. Additionally, I'm not a big fan of Microsoft Power BI, but I haven't tried it out, really. It has some interesting features, but sometimes it feels a bit too verbose.

I would recommend proper planning, especially because you have to build the underlying model that will support your dashboard. This is very important.

Overall, I would rate the solution an eight out of ten. To achieve a ten, they should improve the integration with scripting. Sometimes, dealing with complex reports requires more effort, and that could be really improved.

We've got a third-party provider that consumes our data, and they have QlikView experts or QlikSense experts who visualize and create business-type reporting and insights for our other business users to use.

We do operations and monthly reporting via QlikView. We usually have various types of business use cases for different business units, and it is used for all those reports. We create reports for each of the business units based on their requirements. Our users can log onto the portal and prepare all their reports in one place.

QlikView is old, and we are now moving towards a Power BI environment. We are moving all our reporting over to Power BI.

It is useful to use a tool like this to have a view of data at a point in time. You can extract and create little data sets that you can store, and then over time, you can have a view for tracking changes. Especially when you work with a relational database or a database that's a production database, the data is dynamic, but if you use QlikView, you can take a snapshot of different datasets. In your own time, you can then get insights and report, build, analyze, and draw whatever you need from the data, which is quite useful. So, it is easy to create a data set of specific fields or variables that you need. You create the snapshot, and it then basically stores that into its own little file that you can build over time. 

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.

I have been using this solution for about 10 years.

It is stable. It is resource-intensive, but it works. It is not bad; it is just old in terms of functionality.

It is resource-intensive. So, it is not easy to scale. In my organization, we have about 50 to 100 users who are using the actual QlikView portal to draw reports. We have 5 to 10 users who are building and creating reports.

I have not really used their support. We have experts in QlikView. If we struggle with something, we've got QlikView consultants, and they have expertise. Every now and then, we do contact them if we're having issues with QlikView.

It is of medium complexity. It is not easy, and it is also not difficult. It takes a little bit of time to get the hang of it. If you have some kind of experience in working with these types of setups, it is quite easy to learn.

It has an annual license. It is expensive as compared to other competitive tools that do more for less. In South African rands, we pay about 100,000 to 200,000 a year.

I would recommend QlikView for a small business with very specific data needs. QlikView makes sense for small businesses with a very specific data environment where data is controlled, and there are one or two people requiring the data or reports. For anything bigger than that, there are other more modern tools that you can use at a lesser cost.

I would rate it a five out of ten because there is quite a learning curve for using the tool, and it has been falling behind other tools.

In my manufacturing unit, we use QlikView to track various KPIs related to inquiries, bookings, test drives, retail sales, turnaround times, service attendance, part replacements, and more. We visualize this data through line charts, bar charts, and pie charts, and also offer ad hoc reporting for dealers to customize their dimensions and measures. This helps us monitor performance, identify trends, and make data-driven decisions efficiently.

The most useful feature of QlikView for me is the QVD concept. It allows me to compress and store data, improving application performance by reducing load times. Additionally, I find the access control feature valuable as it enables me to restrict data access based on roles, ensuring data security. Lastly, the ability to schedule tasks using the QMC automates data reloads, keeping dashboards up-to-date without manual intervention.

In terms of improvement, I would like to see more advanced features from Qlik Sense integrated into QlikView to keep it competitive and up-to-date.

I have been using QlikView for three years.

I haven't experienced any issues with stability in QlikView. However, performance may be affected by the size of the application and the number of concurrent users accessing it.

I would rate the scalability of QlikView around an eight or nine out of ten. While it offers strong scalability, Qlik Sense surpasses it with concepts like DashOps and extensions, allowing for more customizable visualizations.

The QlikView support team is responsive and helpful. They address issues promptly and assist in resolving them efficiently. I would rate the support as a nine out of ten.

The initial setup of QlikView can be either easy or difficult depending on the individual's prior knowledge and willingness to learn. A basic understanding of SQL and Excel is helpful for dashboard development.

QlikView is affordable.

Visualizations in QlikView helped me compare sales between different iPhone models and cities, enabling better decision-making. I also used it to track inventory balances and analyze fast-moving parts, helping optimize manufacturing and stock management.

In my experience, QlikView offers extensive customization and flexibility, allowing us to provide pan-India access to around three thousand dealers. Despite having multiple concurrent users, the application remains stable, contingent upon server size.

I would recommend QlikView to others. It offers efficient data compression with QVD, enabling faster reload times. Access control based on roles and field-level restrictions enhances data security. Plus, its user-friendly interface makes it easy for end-users to navigate and utilize.

Overall, I would rate QlikView as a nine out of ten.