student at a educational organization with 1,001-5,000 employees
Real User
Top 5
Jul 9, 2025
Everything depends on the use case, but I would prefer Power BI because of how mainstream it is. There is not much information available. It is not a mainstream tool that many companies use, so if you are doing something that has not been done before, you can find it challenging to get an answer. Unlike Power BI, where there are many examples of what you want to do elsewhere, with QlikView this is not the case. The support for it could be improved. Growing the support online would be beneficial for Qlik. Having more guides on complex tasks you want to do with Qlik would help. There is support online and a Qlik community that shares solutions for common problems, but for quite niche requirements, it does not have that sort of support.
The support aspect could be improved, particularly in terms of response time for high-priority issues, especially when dealing with production environment client issues that require immediate attention. Qlik Sense Cloud pricing is relatively high. While on-premises versions work with user-based licensing effectively, the cloud version's capacity-based pricing needs more clarity. There should be more comprehensive documentation and explanatory videos available to help clients understand and calculate capacity-based pricing, making it easier to predict costs before implementing Qlik Sense Cloud.
Although it can be improved, it stores all the data in the dashboards and its proprietary QED file system, used internally by Qlik Sense. One area of improvement is that it doesn't offer an API for accessing processed data stored in the QED files. There is no provision for an API to retrieve data from QEDs for third-party applications. Providing an API feature to access data from the dashboard or QEDs could be beneficial.
Business Intelligence Architect at a financial services firm with 5,001-10,000 employees
Real User
Top 5
Jan 16, 2025
Actually, I don't have any specific ideas. The last time I built a report for the IT team to monitor their process was about a year ago. They received requirements and tracked progress, measuring how they processed tasks. Power BI offers better pricing compared to Qlik Sense. Qlik Sense has better performance, particularly in its archival system. However, Power BI has better visualizations and interactions with updates in 2023 that provide ease of use. Power BI is more user-friendly than Qlik Sense.
In our company, we found a few requirements in the tool, which we directly shared with Qlik's team through our account manager. With the May 2024 release, the tool has covered a lot of products, but I feel there is more to come. I am expecting new updates in the tool. Qlik Sense requires one to have a lot of technical knowledge. It is an area where improvements can be made.
The communication with the solution's sales managers in Europe is not the best, making it an area that requires improvement. My company usually gets no response from the tool's sales managers. In Qlik Sense, some improvements are required in QMC since it hasn't improved much over the years. QMC is related to the management console, and though it works, it needs improvement. Some improvements in the data load editor should be considered. The load manager has different sections, and it should be possible for the user to deactivate/activate code by commenting/uncommenting at a section level.
Qlik Sense is not meant for writing something from the user interface, which is a major challenge because our company wants users to interact with the reports and to input some comments or data that should get stored into some database. The aforementioned area can be considered for improvement in the product. With Qlik Sense, there is a need for it to provide good performance because if there is a large volume of data, then its performance becomes slow. User interaction or user experience is not that great in that case if the data size or reports are huge. The aforementioned area can be considered for improvement in the product. Right now, we are trying to follow up with some best practices recommended by Qlik Sense, but to be honest, it is not helping us much because we have very large data in a single application, and we are struggling with it. The product should have an interactive and friendly user interface. The use of APIs is not as friendly as it should be in the first place, especially when considering Python scripts and all other scripts, making it an area where improvements are required. There should be some easy way to integrate the product with the aforementioned areas.
Sr Data Analyst at a consultancy with 501-1,000 employees
Real User
Top 20
Jan 16, 2024
There is room for improvement in some ways of increasing the power of visualization. The current visualization features feel incomplete compared to what's available with scripting tools. The current visualizations feel limited. They lack the variety and richness needed for diverse applications. I'd appreciate more options for visually representing data. More customization options would be very welcome.
I would like to see improvements in the Qlik Sense SaaS version, particularly in the front-end capabilities. Currently, the visualization options are limited, allowing only basic actions like adding dimensions and measures with restrictions on the number. Compared to older products like QlikView, there is room for development in enhancing the features available on the front end for widgets and visualizations. Enhancing the formatting options in the SaaS component and making it more visually appealing would be a nice enhancement. Additionally, expanding the library with more versatile widgets would be beneficial. While you can add components from a marketplace or develop your own, there is a need for Java front-end developers to handle this aspect of Qlik Sense.
Direttore Progetti Speciali - Product Business Manager QLIK & Microsoft at Aldebra Spa
Reseller
Top 20
Jan 10, 2024
The reporting solution recently added to the latest Cloud version, since December or January, is not fully developed. The ability to use tabular reporting, like in dashboards, would be a great feature. So, tabular reporting needs development.
One area where Qlik Analytics Platform could be improved is in providing better support for batch processing and traditional ETL workflows. While it excels in real-time replication, it lacks robust tools for handling batch data processing. This limitation can be challenging when there is a need to create non-real-time, batch pipelines for data integration and transformation.
Adoption experience is required. There is some technical background required to do some of the reporting. Customers often request easy interaction with other tools like Excel and PowerPoint.
Senior Business Analytics Consultant at a healthcare company with 10,001+ employees
Real User
Dec 16, 2019
It would be great if decentralized teams would have more features to manage the metadata on the dashboards, setup the specific user access rights and rules to govern incoming and outgoing data sets from/to other teams, and more features to separate the different data process layers (e.g. extraction, transformation [data quality, business rules]).
Qlik Sense is a visual analytics and business intelligence (BI) platform that gives users full control over their system’s data. From this platform they can control every aspect of their system data. It maximizes an organization’s ability to make decisions driven by their data.
Benefits of Qlik Sense
Some of the benefits of using Qlik Sense include:
Easily manipulate data: Qlik Sense allows users to easily combine and otherwise manipulate their system’s data. It allows them to create...
Everything depends on the use case, but I would prefer Power BI because of how mainstream it is. There is not much information available. It is not a mainstream tool that many companies use, so if you are doing something that has not been done before, you can find it challenging to get an answer. Unlike Power BI, where there are many examples of what you want to do elsewhere, with QlikView this is not the case. The support for it could be improved. Growing the support online would be beneficial for Qlik. Having more guides on complex tasks you want to do with Qlik would help. There is support online and a Qlik community that shares solutions for common problems, but for quite niche requirements, it does not have that sort of support.
The support aspect could be improved, particularly in terms of response time for high-priority issues, especially when dealing with production environment client issues that require immediate attention. Qlik Sense Cloud pricing is relatively high. While on-premises versions work with user-based licensing effectively, the cloud version's capacity-based pricing needs more clarity. There should be more comprehensive documentation and explanatory videos available to help clients understand and calculate capacity-based pricing, making it easier to predict costs before implementing Qlik Sense Cloud.
Although it can be improved, it stores all the data in the dashboards and its proprietary QED file system, used internally by Qlik Sense. One area of improvement is that it doesn't offer an API for accessing processed data stored in the QED files. There is no provision for an API to retrieve data from QEDs for third-party applications. Providing an API feature to access data from the dashboard or QEDs could be beneficial.
Actually, I don't have any specific ideas. The last time I built a report for the IT team to monitor their process was about a year ago. They received requirements and tracked progress, measuring how they processed tasks. Power BI offers better pricing compared to Qlik Sense. Qlik Sense has better performance, particularly in its archival system. However, Power BI has better visualizations and interactions with updates in 2023 that provide ease of use. Power BI is more user-friendly than Qlik Sense.
The appearance could be enhanced, especially when compared to Tableau or Power BI. Maybe more AI or real-time analytics could be incorporated.
In our company, we found a few requirements in the tool, which we directly shared with Qlik's team through our account manager. With the May 2024 release, the tool has covered a lot of products, but I feel there is more to come. I am expecting new updates in the tool. Qlik Sense requires one to have a lot of technical knowledge. It is an area where improvements can be made.
The communication with the solution's sales managers in Europe is not the best, making it an area that requires improvement. My company usually gets no response from the tool's sales managers. In Qlik Sense, some improvements are required in QMC since it hasn't improved much over the years. QMC is related to the management console, and though it works, it needs improvement. Some improvements in the data load editor should be considered. The load manager has different sections, and it should be possible for the user to deactivate/activate code by commenting/uncommenting at a section level.
Qlik Sense is not meant for writing something from the user interface, which is a major challenge because our company wants users to interact with the reports and to input some comments or data that should get stored into some database. The aforementioned area can be considered for improvement in the product. With Qlik Sense, there is a need for it to provide good performance because if there is a large volume of data, then its performance becomes slow. User interaction or user experience is not that great in that case if the data size or reports are huge. The aforementioned area can be considered for improvement in the product. Right now, we are trying to follow up with some best practices recommended by Qlik Sense, but to be honest, it is not helping us much because we have very large data in a single application, and we are struggling with it. The product should have an interactive and friendly user interface. The use of APIs is not as friendly as it should be in the first place, especially when considering Python scripts and all other scripts, making it an area where improvements are required. There should be some easy way to integrate the product with the aforementioned areas.
There is room for improvement in some ways of increasing the power of visualization. The current visualization features feel incomplete compared to what's available with scripting tools. The current visualizations feel limited. They lack the variety and richness needed for diverse applications. I'd appreciate more options for visually representing data. More customization options would be very welcome.
I would like to see improvements in the Qlik Sense SaaS version, particularly in the front-end capabilities. Currently, the visualization options are limited, allowing only basic actions like adding dimensions and measures with restrictions on the number. Compared to older products like QlikView, there is room for development in enhancing the features available on the front end for widgets and visualizations. Enhancing the formatting options in the SaaS component and making it more visually appealing would be a nice enhancement. Additionally, expanding the library with more versatile widgets would be beneficial. While you can add components from a marketplace or develop your own, there is a need for Java front-end developers to handle this aspect of Qlik Sense.
The reporting solution recently added to the latest Cloud version, since December or January, is not fully developed. The ability to use tabular reporting, like in dashboards, would be a great feature. So, tabular reporting needs development.
One area where Qlik Analytics Platform could be improved is in providing better support for batch processing and traditional ETL workflows. While it excels in real-time replication, it lacks robust tools for handling batch data processing. This limitation can be challenging when there is a need to create non-real-time, batch pipelines for data integration and transformation.
Adoption experience is required. There is some technical background required to do some of the reporting. Customers often request easy interaction with other tools like Excel and PowerPoint.
It would be great if decentralized teams would have more features to manage the metadata on the dashboards, setup the specific user access rights and rules to govern incoming and outgoing data sets from/to other teams, and more features to separate the different data process layers (e.g. extraction, transformation [data quality, business rules]).
More freedom for custom visuals and dashboard creation would be an improvement.