TrustRadius: an HG Insights company

QlikView Manufacturing Reviews & Insights

Score7.3 out of 10

789 Reviews and Ratings

Community insights

TrustRadius Insights for QlikView are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

High Speed and Agility: Users have consistently praised QlikView for its high speed and agility in data visualization, with many stating that the software allows them to quickly navigate from a high-level view to granular details. This speed and agility enhance the overall data visualization experience, making it efficient and seamless.

Intuitive Data Exploration: The associative search feature in QlikView has received high praise from users for its intuitive and efficient data exploration capabilities. Many reviewers appreciate that it eliminates the need for predefined drill paths, allowing them to visually explore the data and go anywhere they want without restrictions. This feature greatly enhances their ability to analyze data effectively.

Powerful Data Loading Capabilities: Users highly regard the data loading capabilities of QlikView, considering it a powerful platform that can be extended and incorporated into web pages. The ability to integrate with the R open-source engine and build custom extensions adds to its versatility and usability. Several reviewers have mentioned this as a key strength of QlikView.

QlikView Reviews

14 Reviews
ManufacturingAutomotive2Chemicals1Electrical & Electronic Manufacturing1Furniture1Mechanical Or Industrial Engineering3Pharmaceuticals1Apparel & Fashion1Cosmetics1Consumer Goods1Medical Device2

Nice product

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We use to report Key Performance Indicators, financial reports. QlikView allows us to present the data with dynamic graph, filters, erc.

Pros

  • Personalized reports
  • Filtering

Cons

  • Copying data directly from the app

Likelihood to Recommend

It works well to analyze data in graphs, maintain historical data, distribute the data to a large group of people.
Vetted Review
QlikView
6 years of experience

QlikView is Good

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

I use QlikView to combine data from several disparate spreadsheets to analyze and report our market share with our distributor customers throughout the world. "Distributor Customers" is the primary key among the spreadsheets. Since we have over 100 distributors, it would take me a long time to do this analysis and reporting without loading it into QlikView and creating a chart.

Pros

  • aggregating and filtering data from disparate data sources
  • letting users slice and dice data quickly and easily
  • easy to customize formulas and fields to display exactly what you want

Cons

  • The user interface could use some refreshing so it looks more modern
  • The reports that you print out could be more attractive
  • Connecting to and retrieving data from Salesforce CRM could be made easier.

Likelihood to Recommend

I have successfully loaded and analyzed data from html webpages with other data from spreadsheets. QlikView is very easy and intuitive for end users in finance, operations, sales, or marketing to use. I have not encountered any situations where QlikView was not able to handle the amount of data I needed to report/analyze, but if I worked for a Fortune 500 company, I am told that I could run into issues with data volume.

Great Tool for Data Consolidation

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We use QlikView to consolidate data from our ERP system into a single platform that can generate reports, easily extract data, and offer point-and-click functionality. It allows us to analyze our financial and nonfinancial data more effectively and efficiently. We lean on QlikView to manage our data across multiple departments and job functions.

Pros

  • Easy to use
  • Consolidated data
  • Useful across all business functions

Cons

  • Ease of back-end configuration
  • Adjusting modules on the fly
  • Loading speed

Likelihood to Recommend

QlikView is a great supplemental tool to an ERP system. It allows you to customize your data without making changes within the ERP system. It is easy to filter, sort, and sift through data on the fly. The learning curve is very minimal and it is straight forward to use.
Vetted Review
QlikView
4 years of experience

Perfect for data visualizations at the organization or department level

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use it across every department for the most real-time view in dashboard reporting. Whether it's sales, production scheduling, IT system status or performance, etc. We also use it for viewing historical order and sales data. It has been critical for gaining insights into the performance of our organization.

Pros

  • Data visualizations
  • Data warehousing
  • Integrating with 3P software

Cons

  • Steep learning curve.
  • Some dashboard features feel slow.
  • Robust features can feel overwhelming for new users.

Likelihood to Recommend

I believe it's imperative for any growing organization to have a dynamic business intelligence tool and Qlik is among the top 5 options in my opinion. The robust features and integration capabilities make it a great option for all types of organizations, but when deciding between Qlik and other options, it really comes down to preference and compatibility with existing systems since it is very similar to competitor options like PowerBI.
Vetted Review
QlikView
3 years of experience

QlikView user review

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We have many users working with the QlikView app, and export our ERP data to the software to apply filters and research product sales and orders across our global footprint. It can be very challenging to export past data and current trends from most ERP software, and the QV application makes it easy and fruitful in searching for trends and justification data.

Pros

  • Trend identification
  • New product tracking
  • Data export

Cons

  • Alignment across many divisions
  • Data input clarity

Likelihood to Recommend

Sales data validations have helped manage our justifications in the past, especially with regard to new product development and new business introduction. It has also been helpful in identifying trends with business impact and direction specific to quarter and monthly sales from ERP data as well as decisions to purchase equipment of staffing based on run rates and product demand.

One thing that can get out of hand is data output - if you aren't careful in your query, you may be overloaded with data dumps and drown in the amount of info you have to filter through. This is a user caution, not a comment on the software itself.
Vetted Review
QlikView
3 years of experience

QlikView: Decent BI tool

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

QlikView is widely used in a range of reports such as marketing, sales and KPI tracking internally and presentation reports externally. The tool has high-quality graphing options that allow us to provide results to C suite level senior leader team on a daily basis and also generate graphs for analytics.

Pros

  • Interactive.
  • Easy to use.

Cons

  • Costly.
  • Weak integration.

Likelihood to Recommend

QlikView is well suited for business analysts who need to provide daily reports but do not have decent knowledge of the current free data science tools such as Python and R, which have much higher learning curve to master. In this case, QlikView provides a comparably easy-to-use alternative.
Vetted Review
QlikView
4 years of experience

Powerful Data Processing and Reporting Tool

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

We use this with a few of our projects on the analytics team. We use it for KPI reporting, sales reporting, and marketing reporting.

Pros

  • Robust In-Memory Technology: data can be stored in-memory and you can access the reports quickly.
  • Compresses the data to one-tenth of the actual size.
  • Powerful data searching technology.

Cons

  • Customer support could be improved a bit.
  • The learning curve is high compared to other BI tools.

Likelihood to Recommend

Well Suited:
  • If you are well versed with other BI tools, doing complex calculations will be easy. Otherwise, you might need an expert to handle those.
  • If you have a huge dataset and are looking for quick calculations.

Not well suited:
  • If you are a small company, licensing is going to be challenging. Also, you will require the necessary infrastructure to handle this load of the tool.
Vetted Review
QlikView
3 years of experience

QlikView goes deep into QuickBooks data -- a little training takes you a long way

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

My clients use QlikView (or I should say that I use QlikView for my clients!) to build reporting and "dashboards" based on accounting and operations data. Primarily, we use the version bundled inside of QuickBooks 2015 Enterprise (called "Advance Reporting"), and have created very nice -- and quite complex -- reports based on the QlikView engine / modules. Specifically, we report on sales commissions earned by sales person, on a per-item, per customer basis -- great detail that is simply not possible without QlikView.

Pros

  • QV's #1 strength is the drag and drop visualization tools -- with just a bit of training, you can make some really nice looking charts
  • QV's #2 strength is the simplicity of the filtering. Other SQL languages might call this "linking" or database structure ... which can be a pain.... but QV makes this easy. Further, once the data is inside QV, the ability to FILTER the data using check boxes is completely intuitive and simple.
  • QV's #3 strength is its ability to work across platforms and integrate multiple data sources and multiple types of data. QuickBooks data is just one example of something that it can chew up with ease.

Cons

  • Like a lot of software, QV starts with a blank page. If you are like me, you dive in without reading the instruction manual. Big mistake. There is a rigid stepwise process that you must follow to make it work....
  • I've never used anything quite as powerful as QV, so I cannot compare this to many other packages. ... but with 30 minutes of training and an hour of practice, you can be pretty proficient.

Likelihood to Recommend

QlikView is well suited for QuickBooks uses -- particularly if you are running 2015 Enterprise or later. It's not perfect for those organizations that are trying to push data analytics down to the staff/user level ... I think it is still best suited for a knowledgable IT or SQL geek on the startup process. But if you can get a geek (like me) to design your reports, then any staff person can use the reports and even make simple updates (like sorting on a new date range, or selecting different filters).

QlikView is a beast but great at slicing and dicing data!

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

QlikView is used across our whole organization. In the marketing department we use it for Business Intelligence to view margin, cost, categories, etc. It gives us really granular info about our skus and sales. I personally use it to decide which products to promote in marketing campaigns based on margin and bestsellers. We've also needed to understand the cost of an item in order to decide on promotions.

Pros

  • I love how you can slice and dice data to get the answers you need about your skus and sales.
  • QlikView gives me more detail than Google Analytics about how my categories are performing.
  • Our BI team is able to use QlikView to answer almost any question I have about what's happening on our website. They can set up bookmarks of commonly used searches that I need to make it quicker for me to find the data I need.

Cons

  • QlikView is not intuitive for the average user. You definitely need a BI team to set it up and help you use it, as a marketer.
  • Our instance of QlikView does not provide cost data. I'm given the information I need but I have to do some math in order to come up with the cost we're selling a product for. This may be because our BI team hasn't set it up that way.
  • You have to remember to use QlikViews navigation functions and not your browsers. And when I click from one tab to another, I lose my settings and have to start over.
  • I'm a casual user of QlikView and maybe if I were an actual BI team member, I would have the knowledge to get around these obstacles.

Likelihood to Recommend

If you don't have a Business Intelligence team to set it up and help you navigate, then QlikView is not for you. It is definitely an enterprise tool. I have to ask someone on our BI team to walk through any process that is different than what I'm normally doing in QlikView. You don't inherently know which tab to start with whether it's the Product, Marketing, or Trends tab. But it houses a lot of data is very powerful. I would love to have the time to really understand the tool and make more use of it in my day-to-day decision making.

QLV: Great Data Discovery and Data Association tool. Strange marketing.

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

QlikView was used for support of ETL, data integrity between different/disparate prod. sources, and discovery of data gaps.

Pros

  • Associations between disparate sources.
  • Entities that are NOT used/NOT associated (although supposed to be).
  • N-LOOKUP/hierarchical data visualization (example: hierarchically organized Operational codes, prices, business conditions and busn programs).
  • Makes good compression of data for up to 100 Mln transactional rows (I have compared head-to-head with SSAS cubes=not indexed). QLV works faster. Give QLV at least 32 Gig of RAM on 64 bit architecture, you will see the instant response for many millions of transactions, with instant grouping and counters.
  • Data extraction from sources is separated from graphical part. This means you can provide ETL part (extract/periodical extract from sources) separately, and populate QVD (intermediate compressed format for all users). All users will connect their QLV reports to this QVD format, thus NEVER loading/affecting the (OLTP/DW) source at all.
  • GUI interface is simple enough. Copying of the controls is simple. Filter selections, made in the controls by user, are saved by default/reproduced on QLW report closing/reopening. In other words, user keeps his/her specific business context. "Current Selections" (a simple GUI control) allows to visualize the business context.
  • Actions/Triggers (on a document/tab or user level) allow to pre-populate user filter selections.

Cons

  • Outrageous marketing: all QLV manuals start with the words; "Lets take a flat file as Data Source". Information is NOT supposed to be kept in Flat files. This is written in the Chapter 1 of any Introduction to Data Processing text book in the world.
  • QLV first mentions of the POSSIBILITY of the connection to relational DB on the page 200 of the QLV manual(!). In fact, the Relational Data base source is the "second class citizen" in QLV. You have to go into data extraction Script, instead of just specifying OLE DB or ODBC as a data source!
  • Qlikview sales people could answer the simple question: does QLV work against relational DB- yes or no? Their answer was: "The question is too technical". The company clearly does not understand how to position its (absolutely wonderful) product. As a BACKEND data discovery and analysys product.
  • They will NEVER EVER use the word: "Relational DB Source" and "Powerful ETL capabilities" in their marketing. It is 100% concentrated on GUI part/interface and their QVD (compressed proprietary format) storage. NOT on real-life data extraction from real DB source. That is a shame, Marketing department does not understand their target audience.
  • QLV help files are rudimentary, do not give good examples on actual DB data extraction and analysis. They might have done it on example of Microsoft Sample Databases - this was never done.
  • You can specify the % of RAM memory consumed by QLV. On reaching this percentage, QLV, unfortunately, becomes unresponsive. Abort (of the running script) does not work well. Modality of the script window and of help files is not chosen correctly. QLV may hang and crush on large data.

Likelihood to Recommend

QlikView is well suited for:

  • Existence of duplicates, data gaps, missing data.
  • ETL delivery (validation/direct comparison, driven by hash values on source and target).
  • Operational processes with multiple (disjointed/independent) sources.
  • Flat and XML file comparison.
In a situation of 20-30 different entities, QlikView will "join everything to everything" and will show what is associated with what - by DEFAULT - going through a large number of intermediate joins. It will do it in a sub-second time with up to millions of entities. In 70% of the cases you will see correctly joined/pertinent data.
However, to go beyond, you will need to introduce meaningful composite keys, hash values for columns being compared, review case sensitivity of the values, analyze for cross joins/absence of relationship for some of the entities.