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

The golden source

We've said there should be one version of the truth for data. There should be one version of the truth for your document too.


You may not be familiar with the expression "golden source", but it's a concept you should become familiar with.


Because a QlikView document contains both code and data, it is more difficult than in more traditional environments to keep track of code changes. Add the fact that it is more or less impossible to assimilate all the code and settings for a QlikView document in one place and compare them to another version of the same document, and you have something of a maintenance problem. Without the suitable tools, you would need discipline if you are going to keep a code version that you can rely on as the production version.

How to do it

I can hear you saying, "the version in production is the real, latest version". Okay, maybe it is if you strictly enforce a "no change to production code" rule. But what if it can be easily bypassed...