Book Image

QlikView Unlocked

By : Andrew Dove, Roger Stone
Book Image

QlikView Unlocked

By: Andrew Dove, Roger Stone

Overview of this book

QlikView Unlocked will provide you with new insights to get the very best from QlikView. This book will help you to develop skills to work with data efficiently. We will cover all the secrets of unleashing the full power of QlikView, which will enable you to make better use of the tool and create better results for future projects. In the course of this book, we will walk you through techniques and best practices that will enable you to be more productive. You will gain quick insights into the tool with the help of short steps called ”keys,” which will help you discover new features of QlikView. Moving on you will learn new techniques for data visualization, scripting, data modeling, and more. This book will then cover best practices to help you establish an efficient system with improved performance. We will also teach you some tricks that will help you speed up development processes, monitor data with dashboards, and so on. By the end of this book, you will have gained beneficial tips, tricks, and techniques to enhance the overall experience of working with QlikView.
Table of Contents (16 chapters)
QlikView Unlocked
About the Authors
About the Reviewers
Hidden Image List

Is this the right place for this data?

It can be tempting to try to build everything into one document to save on QlikView licenses. Here, we will explain why this is not a good strategy.


There are often good reasons to want to cram as many features or disassociated data as possible into a single QlikView document, but this is rarely the best strategy and can ultimately lead to difficult and expensive rewrites. Keep logically different applications in separate documents and take the hit on QlikView license costs because, ultimately, this will be cheaper and save you lots of time.

How to do it

We can't always anticipate how a QlikView document will evolve, and even the best-designed application could eventually become unwieldy and inefficient over time. Often, this is caused by adding in data and features that would be better in a separate document. It's common to see QlikView documents that should logically be two or more documents, with unrelated data models or simply too many features...