Book Image

Creating Stunning Dashboards with QlikView

By : Julian Villafuerte
Book Image

Creating Stunning Dashboards with QlikView

By: Julian Villafuerte

Overview of this book

QlikView is one of the most powerful analytical tools in the market. Based on an in-memory associative model, it lets users freely navigate through the data, spot trends and make better decisions. This platform is capable of integrating a wide range of data sources like ERP systems, data warehouses or spreadsheets into a single application in order display dashboards with state-of-the-art visualizations. Creating Stunning Dashboards with QlikView is an easy to follow handbook that guides you through the process of creating an effective and engaging dashboard that delivers tangible value to the business. It starts with the identification of the business needs and the definition of the main KPIs, and takes you all the way to the application rollout. Throughout the book, you will learn how to apply some of the best practices in the field of data visualization, create a robust navigation schema, chose the best chart types for each scenario and many other things that will help you create effective dashboards that uncover all the stories behind the data.
Table of Contents (16 chapters)
Creating Stunning Dashboards with QlikView
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
4
It's Not Only about Charts
Index

Folder structure


Once you get used to QlikView's development style, it is easy to create new applications from the scratch disregarding its folder structure, the location of its data sources, or the overall portability of the environment. However, these elements are not to be ignored as building unstructured apps usually leads to inefficiencies and rework.

Having a robust yet simple folder structure available to start new dashboards will ensure that all your endeavors can be easily integrated with the current QlikView environment or moved around on different computers.

This structure will greatly vary from environment to environment, and it depends on the number of developers involved, the workload distribution, the complexity of the data sources, and even the personal/organizational styles. Nonetheless, it should be able to handle several applications (not only different modules, but also different versions of each one of them), a layered QVD structure (files and generators), general files...