Book Image

Mastering Qlik Sense

By : Juan Ignacio Vitantonio
Book Image

Mastering Qlik Sense

By: Juan Ignacio Vitantonio

Overview of this book

Qlik Sense is a powerful, self-servicing Business Intelligence tool for data discovery, analytics and visualization. It allows you to create personalized Business Intelligence solutions from raw data and get actionable insights from it. This book is your one-stop guide to mastering Qlik Sense, catering to all your organizational BI needs. You'll see how you can seamlessly navigate through tons of data from multiple sources and take advantage of the various APIs available in Qlik and its components for guided analytics. You'll also learn how to embed visualizations into your existing BI solutions and extend the capabilities of Qlik Sense to create new visualizations and dashboards that work across all platforms. We also cover other advanced concepts such as porting your Qlik View applications to Qlik Sense,and working with Qlik Cloud. Finally, you'll implement enterprise-wide security and access control for resources and data sources through practical examples. With the knowledge gained from this book, you'll have become the go-to expert in your organization when it comes to designing BI solutions using Qlik Sense.
Table of Contents (16 chapters)

Qlik Sense Data Modeling

Data modeling is, from my point of view, one of the key components of every data project. From my early start as a consultant in Los Angeles and New York City, modeling was paramount to any project. I would spend 60% of my time analyzing requirements and designing the model. I learned from the beginning that a good data model saves time and headaches in the future.

A good model applies to any tool. From the old OLAP cubes to the newer tools, such as Qlik Sense, if you know modeling, you will be talking the same language like many others worldwide.

Back in the days when I was working as a business intelligence consultant in Italy, we had to migrate a project from OBIEE to QlikView (version 10 back then). Everything changed but the model. The source tables remained the same, the business rules, the logic within the ETL - all the same. The rest, of course...