Five things you need to know about QlikView 12

Here are the 5 things you need to know about QlikView 12

1.) Better, Faster, Stronger (Back-End) Engine

Qlik swapped out QlikView’s old engine in favor of a “2.0” version of the QIX engine that currently powers Qlik Sense. This means a modern, newer back end providing better compatibility across both View and Sense data models, improvements on performance (specifically wide tables), and better data indexing while also offering a seamless upgrade from QlikView 11 to 12.

Everything about this makes sense; the move towards deeper Qlik platform compatibility has definitely been anticipated and is very welcomed for developers working across the two platforms. This also means that future improvements to either View or Sense will improve the other, so less headache between platform differences (see #2 below) and more capabilities to utilize both platforms harmoniously.

2.) Integration of Qlik Data Market

One of the new features in Qlik Sense is the Qlik DataMarket, the easy to use “data as a service” provided by Qlik to pull a very comprehensive library of data sets from trusted providers, such as weather, demographics, census data sets, etc. Before now, if you wanted to use this data outside of Sense, you had to store the data out to a QVD file and subsequently load the QVD into QlikView. Not anymore. The connector is available to download immediately and can be accessed like any other database provider within the QlikView load script.

3.) Easier Access to RESTful APIs

Going even further with enhanced connectivity to external data sets, QlikView now easily integrates with RESTful API connectors. With this connector, also available for download from Qlik’s website, users can now connect directly to data providers and other contact management systems that offer a RESTful API. Think Facebook, Twitter, LinkedIn and a number of other web-based data services providers. This means you no longer need an extension or other applications to access this data; you can pull it directly in through the edit script.

Oh, and it’s also available for Qlik Sense!

4.) A Better Mobile Experience

For those that consume QlikView content via mobile devices, frustration can occur when you try doing something that you ordinarily do within the same dashboard on the Access Point. 

With QlikView 12, many of these frustrations will go away. Qlik has worked very hard to improve the mobile experience making working between Access Point and the mobile version feel very natural.

Here are some of the things you’ll now be able to do on mobile:

5.) Forward Thinking Improvements to Security

In our ever-changing BI landscape, security needs and requirements continue (and will continue) to change. To meet this current demand and keepthe future in mind, Qlik included more than 100 security improvements to QlikView 12, including better encryption, better client request handling and improved XML parsing. Qlik’s goals in this attempt are to “future-proof” QlikView and provide the ability to consistently keep up with the pace of best practices changing within the industry down the road.