Book Image

Hands-On Business Intelligence with Qlik Sense

By : Pablo Labbe, Clever Anjos, Kaushik Solanki, Jerry DiMaso
Book Image

Hands-On Business Intelligence with Qlik Sense

By: Pablo Labbe, Clever Anjos, Kaushik Solanki, Jerry DiMaso

Overview of this book

Qlik Sense allows you to explore simple-to-complex data to reveal hidden insights and data relationships to make business-driven decisions. Hands-On Business Intelligence with Qlik Sense begins by helping you get to grips with underlying Qlik concepts and gives you an overview of all Qlik Sense’s features. You will learn advanced modeling techniques and learn how to analyze the data loaded using a variety of visualization objects. You’ll also be trained on how to share apps through Qlik Sense Enterprise and Qlik Sense Cloud and how to perform aggregation with AGGR. As you progress through the chapters, you’ll explore the stories feature to create data-driven presentations and update an existing story. This book will guide you through the GeoAnalytics feature with the geo-mapping object and GeoAnalytics connector. Furthermore, you’ll learn about the self-service analytics features and perform data forecasting using advanced analytics. Lastly, you’ll deploy Qlik Sense apps for mobile and tablet. By the end of this book, you will be well-equipped to run successful business intelligence applications using Qlik Sense's functionality, data modeling techniques, and visualization best practices.
Table of Contents (18 chapters)
Free Chapter
Section 1: Qlik Sense and Business Intelligence
Section 2: Data Loading and Modeling
Section 3: Building an Analytical Application
Section 4: Additional Features

Link table

In the preceding section, Data modeling, we learned about the star schema, which includes one fact table and multiple dimension tables. But in the real word, there are situations when we need multiple fact tables in the data model. In such a situation, we can use two options to link them together. One is by using concatenation, and the other is by using the link table. If the granularity of the fact table is similar, we can use the option of concatenation, but if the granularity is not the same, we should use the link table option.

The link table concept requires three things:

  • You need to create a composite key in each fact table
  • You need to create a link table (which has common fields from both the fact table and composite key)
  • If you have created the link table using resident load, you should delete the fields from the resident table that you have loaded in the link...