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

Deploying from development to UAT and on to production

There are a few things to remember to do as your nice new document goes through testing and on into production.


Always use a consistent approach and document it so that everyone in the team works in the same way.


One of the most common reasons for applications failing when deployed to UAT or production is the fact that file paths are hardcoded.

How to do it

Keep your application in self-contained folder structures and use relative references to files used within it.

Use the same network account to run QlikView services on all machines.

If there is a need to identify which server you are running on, use the ComputerName() function in your script. Alternatively, you could use $(Include=filename) or preferably $(Must_Include=filename) to set a variable.

If you use an include file, keep the name the same in all environments but change the contents as appropriate to the environment. So, for example, you may have an include file...