Sometimes it makes more sense to use a QVD to load your data from than the source. This might be for testing, performance or development reasons or maybe just because the day ends with a ‘y’.

This script is an example of how to loop through all of the tables in a data model and create a series of QVDs. There is an optional variable (vDebug) you can use to trigger whether this works.

The script should be placed after all the other processing eg on the last Tab or Section.

Data comes in all shapes and sizes and sometimes, the users of the data want to see this as a series of metrics eg as key performance indicators. As always, there are not of ways of handling this and for a quick way in Qlik Sense you can use some generic logic to build a KPI data set that you can keep expanding.

Qlik Sense supports a really simple process for importing a series of files that have the same structure (think a collection of daily comma separated files). You can simply use a wildcard when load the file and that is great but if you need to go back and link the data to the source file you need a different approach.

One of the really clever features of Qlik’s data apps is the ability to have tiers of security. If you are familiar with Section Access then you may have either wondered or worked out how to simplify security with a tiered model.

This example supports creating user specific dynamic bookmarks. This is great where you may have a use case where a user can see all of the data (ie no section access) but for usability reasons, users should have a default element assigned relevant to their organisational structure.

This is a follow on from the last Qlik post on basic reload statistics.

If you want deeper analysis you can use this Qlik script to capture one or more specific table reloads in an app.

This code is useful for capturing reload statistics in a single app:

• reload start and end time

• reload duration

• user executing the reload

• computer executing the reload

This is a standard block of Qlik script we use for creating a calendar via a resident load.