QlikView Reviews

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.

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. 

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.

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.

The ability to capture data from multiple sources, quickly link by key fields and quickly analyse in a dashboard proved to be such powerful features that we reduced the use of Microsoft Excel and Microsoft Access almost entirely for any kind of reconciliations.

I worked in a financial institution having most data in mainframes but also having extracts and datasets put into various places from highest quality Oracle and MS SQL server objects right down to MS Access/Excel and continuing to Text File output.

Sometimes for either quality control purposes daily or some other kind of reconciliation or verification, QlikView was great for a basic end user with minimal skill to bring that data in and map it as necessary to achieve the desired result. (Often the datasets easily map via a couple of primary fields that the business users understand and outside developers may not understand without a business analyst specification)

Most times making that ad hoc effort a template of some sort and making mundane roles like daily recons be easily achievable.

Doing this same work in MS Excel or MS Access can be tricky and dangerous and not be as intuitive for non-technical people. Doing it other ways can end up being too much effort with hiring developers and building systems and paying for a lot of developer man-hours when a quick QV dashboard does the trick by the business end user.

This product improved how my organization conducted repeatable analyses, such as a user access internal audit review for 500 users over 100,000 user ID and system access across 50-100 systems. My first project before we had QlikView took about a month, but after we rewrote the procedure using QlikView, it was much better and took about a week. We pretty much used the same raw data, but the report and analysis was so much quicker.

The process of gathering the data and using Microsoft Access used to take a month or so. Certainly, using QlikView as an ad-hoc tool is very powerful, yet easy. Comparing it to development on Microsoft Access, it feels about 10 times quicker. You go from raw data almost directly to reporting. (Skipping the hassle of lots of queries, forms, and slow report creation.)

As they say, "Seeing is Believing”.

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.

The feature I found valuable in the solution is the power of VPN and the power of representation of data. Also, the speed of performance is a valuable feature of the tool.

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.

1. QlikView Scripting - Takes some time to learn, but it is very powerful. Not as a total ETL replacement tool necessarily, but as a supplement to load and join data sources, perform additional transformations, add supplemental inline tables, and even at times, output a final .txt/.csv for consumption by other tools (even Tableau!). I've combined as many as a half dozen data sources including data from multiple SQL Data Marts, Teradata Data Marts,Source System DBs, XLS, CSV, and Google Big Query.

2. Design Flexibility - While other products may do drag and drop, ad-hoc reporting analytics better. (Including Tableau, and Qlik's new product QlikSense) I've not come across one that better supports the creation of a polished, packaged, custom dashboard, that supports what I'd consider "guided exploration", and best meets the needs of our user base. The customization can be taken even further through in-house built, or borrowed, extensions (e.g. Custom D3 Visualizations).

We have gradually reduced laborious manual reporting in Business Units and "spreadmarts". We now have some executive using QV dashboards in weekly review meetings, in place of spreadsheets and PowerPoints. While it does take some time and IT involvement to initially develop and deploy a solution, the payback is immediate. In one particular case we were able to eliminate a days worth of manual work with a QlikView solution that required a few days of development effort. We also previously had no way for end users to routinely and easily analyze larger (100 Million+ rows) data sets, which now can be done through QlikView.