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)

The properties panel

The properties panel is, in the author's opinion, one of the most valuable things about extensions in Qlik Sense and the general extensibility of the product as a whole. The property panel is the configuration interface between the JavaScript code and the self-service user or developer.

As such, it is essential to leverage and understand the property definition file.

First and foremost, it is recommended and best practice to capture the property definition in a separate file and load it via RequireJS to your main JavaScript file. This is done fairly simply by creating a new JavaScript file in the folder structure, suggested to be called properties.js:

In the MasteringQS.js file, you load the properties module by defining it in the top of the file structure:

define(['./properties', 'text!./template.html'],