BillionRows.com would like to start series of articles about best practices in QlikView. We know that there are thousands articles on the same topic, but we would like to share our point.
First we would like to differentiate two main roles during development of QlikView application. First role is the Developer, who is responsible for the scripting part and Designer, who is responsible for the design of the application. Of course the roles are not so straightforward, also the responsibilities.
There are several main points to follow in order to perform awesome design of your application.
- Same objects, same position in different sheets or design consistency across sheets
This is very important rule to follow. It is very important your application to be consistent. When there are several occurrences of same object in different sheets, they must be on the same position. Try to follow this rule and your user will be more confident using the tool.
- Carefully with colors
You should use contrast/focus neutral colors for your application. There are several research reports that people read better data presented with neutral colors. Also try to use the contrast for outliers, just to emphasize that.
- Current selection object on every sheet on the same position
The same rule as point 1, but with selection box. It is very important user to know the current selections. For us current selection box is the most important object for every application. Usually we put it at to left position.
- Always include Help/ How-to sheet
It is a good design practice to include one sheet with information, how to use the application. It is important users to be familiar with QlikView functionality. Example image for your How-to sheet:
- Use common variables for expressions
Always you need to use several same expressions across many sheets and objects. It is a good practice to create one repository file with all expressions. During reload it is easy to create a loop, which would create variables from the expressions in your repository.
- Use calculated conditionals on large charts
It is common practice to use calculated conditionals. Sometimes it is very important to use it when you are dealing with large tables or ‘heavy’ objects. QlikView does not use any resources (RAM) for minimized objects, objects without fulfilled conditionals and not active objects in container.
- Naming conventions
Try to follow a naming convention for all your object titles and user fields. Do not leave unfamiliar database names to be presented to the end user. We have seen prefixes or suffixes in so many applications, which confuses users. If you like a designer are familiar with the naming and content of the different fields does not mean that end users are.