QlikView Reviews

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.

We employ it as both an ETL tool and a visualization and analytics platform. It provides interactive visualizations and business intelligence capabilities.

The most valuable aspect is its extensive library on Microsoft, providing a robust framework for implementation.

Enhancing user-friendliness would be highly beneficial. It could become even more remarkable if it were available in the cloud, retaining the core functionality of its engine and offering the same seamless user experience. There could be enhancements to the Qlik Management Console. Specifically, the user interface and user experience could be refined to better manage execution sequences. Currently, there might be overlaps between executions and deployments without clear alerts or notifications. This lack of alerts could lead to issues like concurrent job executions causing system downtime or memory constraints. Improving the sequencing of deployments and incorporating smart notifications would significantly enhance the overall process.

I have been working with it for ten years.

I would rate its stability capabilities eight out of ten.

Scalability is paramount, given that it often constitutes a significant cost for companies. Initially designed for around thirty users, our server infrastructure has undergone notable expansion over the past two years. We've exceeded hundreds of users, particularly with large clients like the government, who now boast a user count surpassing a hundred. I would rate it seven out of ten.

The community around it is robust, and I am extremely pleased with the level of support they provide. I would rate it ten out of ten.

Positive

Before adopting QlikView, our team previously utilized SAP's Business Objects for scalable enterprise solutions. Tableau was also present in the market at that time, predating QlikView's emergence. I found Tableau to have an element of complacency. However, upon transitioning to QlikView, I perceived it as a superior and more dynamic solution.

The initial setup was quite straightforward. I would rate it ten out of ten.

Getting the dashboard up and running typically doesn't take much time.

It's reasonably priced and falls on the more affordable side. The annual cost for this, including server licenses, was approximately thirty to thirty-five thousand dollars. I would rate it five out of ten.

Overall, I would rate it ten out of ten.

Within our customer base, we have manufacturing companies that produce goods like machine pumps, and these firms rely on QlikView for their production processes.

Our clients are looking for a migration process that's as trouble-free as possible, and Qlik Sense is doing well in areas such as database connections and integration, including in SaaS environments where QlikView is still a valuable option. It excels in supporting database connections and various database types.

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.

I have almost twenty years of experience with it.

I would rate its stability capabilities nine out of ten.

It offers excellent scalability abilities. I would rate it ten out of ten.

I would rate their technical support eight out of ten.

Positive

The initial setup was straightforward. I would rate it nine out of ten.

The deployment process involves linking various units and requires careful project planning, including determining the necessary components, deployment strategies, and the overall timeline for the entire process. The duration can vary significantly, typically spanning from one week to several months, contingent on factors like the complexity of the customer's needs and any difficulties encountered during the migration or the implementation process.

It is quite expensive, rating at around nine out of ten on a cost scale. This is mainly due to the requirement for a dedicated ClickView infrastructure as the sole SQL solution. We are primarily using perpetual licenses at the moment, and it's essential to note that we currently have just one SQL solution, which comprises one two-cluster. This incurs a cost of €21,375 for the solution in the current setup.

It is highly valued by our customers as a powerful tool, but it must continue evolving and staying relevant. Overall, I would rate it nine out of ten.

We use the product for data analysis, sales operations, and sales demand planning and forecasting.

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.

We have been using QlikView for three years.

I haven't come across any stability issues for the product. However, a particular error keeps surfacing whenever the threshold for the number of onboarded users crosses the limit.

I rate the stability a five out of ten.

We have 30 QlikView users in our organization.

The technical support services are good. However, they could prioritize critical issues. This particular area needs improvement.

Neutral

We use SAP Crystal Reports.

I rate the initial setup process a seven out of ten. It took half a day to complete product testing and implementation. We receive support services from the vendor for maintenance.

QlikView is more expensive than SAP Crystal Reports. It could be improved. I rate the pricing a five out of ten.

We extensively use QlikView for data visualization and analysis in our organization. It connects to ETW and Data Mart, helping financial executives visualize the data. It has user-friendly data visualization features, supporting our decision-making process with its business intelligence capabilities.

The integration between Qlik Sense and QlikView has proven most valuable to our business. Its speed and efficiency in processing large datasets proved moderately beneficial for our organization, with some performance challenges arising during complex joint operations.

It is a good tool to use and has efficient data visualization features. I rate it a 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 use this solution for ETL, Analytics, Reporting, Automation, Integration between data sources (cloud, local, spreadsheets, etc), Data Scrub for Migration to new software, and automation of sending files to banks instead of using EDI, Positive Pay, etc.

This solution has simplified getting to and understanding our data, no matter where it is housed.

The most valuable features are the ETL, automation, and ease of use by the user population.

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;

excellent

excellent

I have never worked with Qlik Customer Service directly.

no

it wasn't bad. We did need some consulting advise on the set up in the server...but designing the organization and naming conventions should be up to you.  We took the consultants advise and ended up renaming, changing almost everything as far as naming conventions

started with a consultant, didn't use them long.

keep working with the Company to get the pricing you need.  

yes - many

We use QlikView in combination with Salesforce. It provides convenient business analytics and sales tracking. QlikView provides access to data offline. I use this option most often since I can get important information wherever and whenever I need it. 

QlikView is quite intuitive. Its interface looks like Excel. It's cool due to the fact that it provides convenient filtering options.

QlikView has helped improve several aspects of our organization. For example, it provides us with a deeper understanding of our sales and customer service processes. 

Thanks to QlikView, our sales teams now have access to real-time information, enabling them to prioritize leads, identify bottlenecks, and close deals more efficiently. 

The most valuable features of QlikView for our organization have been its robust data analysis and visualization capabilities. In addition, the integration with Salesforce has helped us gain access to crucial sales data in real-time. Salesforce is a reasonable price compared to other applications. 

While QlikView is a powerful tool, there are areas where it could be improved. There is a lack of static PDF report generation and automatic resizing of the dashboard to fit the device, for example. 

Also, scripting can be a bit difficult if you don't have the necessary knowledge, so this app may not be suitable for everyone. 

I've used the solution for about six months.

I use different apps with Salesforce. They include Tableau, Conga Grid, and Rollup Helper. I haven't switched. I'm researching the best solution.

I evaluated Tableau, Conga Grid, and Rollup Helper.

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.