17 Qlik Experts Reveal Their Favorite Tips

Qlik Expert RoundUp Featured Image

All of us QlikView and Qlik Sense developers, regardless of expertise, are always clamoring for the best tips and tricks. There’s the tried and true foundational advice I continually remind myself of. Then we have the little secret tricks whispered from the sidelines at a Qlik event. And everybody loves the tip that is so obvious, I wonder why I didn’t think of it.

I was fortunate enough to convince some of the biggest names in the Qlik universe to provide their favorite QlikView and Qlik Sense tips. The contributors below consist of Qlik blog authors, current or former Qlik employees, and Qlik Luminaries. So let’s get on with the tips and tricks.

Richard Pearce

Richard PearceQlik Central

Think about your data.

More time spent on your data model pays off with even less time to create your User Interface. This is especially true when you’re developing on Qlik Sense. One of the key benefits of the tool is that users can easily create charts and expressions, and as such, developers need to ensure that data is simple, the fields are descriptively named, key fields are hidden and all those extra fields (aka baggage) that aren’t needed get removed!

In the old days QlikView developers could get around a less than perfect data structure with clever expressions. With Qlik Sense you need to change the way you approach a project and think about the user self-service experience once the dashboard is live.

Adam Cooke


Check out the derive functions for building calenders in Qlik Sense. This eliminates the need to script  a traditional date calendar along with all the associated linking issues.

Also try using the engine API explorer and chrome developer console. You might get a sneak peak into new features Qlik may be putting in the next release.

Juan I. Vitantonio

Juan I VitantonioBusiness Intelligence Experience

Resident loads? Loading the same table several times? Forget about SQL-like techniques to create calculated fields when loading data in Qlik Sense/Qlikview.
Preceeding load is your friend and you should keep it on your side. Preceeding load allows you to create or modify field contents while being loaded into memory without the need the table again in a resident load.
Simply add a Load statement before your SQL SELECT or Qlik Load statement and you are good to go! Add as many preceding loads as needed, always keeping an eye on performance.

Dmitry Gudkov

BI Review

My favorite tip is to use QViewer to inspect resident tables when running the script. Check out the full setup: Hints and tips on using QViewer for inspecting resident tables in QlikView

LinkedIn LogoWe also compiled tips from Qlik developers on LinkedIn. Scroll to the bottom of this post below to get these extra 9 tips.

Dalton Ruer

Qlik DorkDalton Ruer

I am a really firm believer that numbers are completely meaningless without providing a context by which they can be digested. The gauge is a chart type that is so “sexy” for many that they use it to blindly display a number like 150. While it may look prettier than a simple text box it virtually tells us nothing. In order to provide the Red and the Green we have to fake the range of values. Which means that they needle position is then misleading. Consider the following 2 gauges. First is a range from 0 to 250, while the second is 0 to 200. Clearly the user takes away something different depending on the “faked” range that we provide.


I’m not suggesting you create a plain/ugly dashboard with nothing but text boxes. My tip is to make the gauge display something meaningful if you are going to utilize it. Instead of just showing the number how about showing it in relation to other values. 0 represents the statistical average of all of the dimensions and the needle then shows where this value lies in relation to 1 or 2 standard deviations away from the average. If the needle is in the white it basically means there is nothing to see here. The dimension is slightly better than the average of the other dimensions but there is no reason to pat anyone on the back. If the needle is in the green it means it is at least 1 standard deviation under the average in which case that is something the user should care about. If the needle is in the red it is time to make some process improvements. Providing a well thought out context helps convert data to knowledge that can drive actionable intelligence.


Patrick Tehubijuluw

Patrick TehubijuluwQlikShow

Work your way back from the end to the beginning. Make it as easy as possible. That is what makes a good design. And otherwise ask yourself: How could a classroom full of 12 year olds, make sense of this?

Ralf Becher


One of my favorite Qlik functionality is blazing fast Mapping with ApplyMap/MapSubstring. I’m using this a lot for unusual purposes like the format and pattern coding you can see in my app Pretty Fast Pattern Collector or to implement phonetic algorithms like Metaphone and Cologne Phonetics for German language in the TIQView data profiling app.

Another interesting and powerful, but not often used function I like is Correl().

Vlad Gutkovsky

vlad-gutkovskyInfinity Insight

Did you know that you can use QlikView Desktop to check the validity of any QlikView license, even Server/Publisher, and generate an LEF? Open QlikView Desktop and Select Help >> License Update.


There is actually an invisible button in this dialog box. Hold down Ctrl+Shift and click in the “space between the buttons” to select the secret invisible button.vlad-secret-button-02

You can then enter any license key you like into the resulting “License Key to Check” dialog and the LEF will be returned!vlad-secret-button-03

Shilpan Patel

shilpan-patelLearn QlikView

QlikView offers a powerful set of ETL functions but many of them fail silently. Peek and ApplyMap are examples of functions that might fail to generate good results yet not provide an error. Always validate your data model after making any changes to your script.

Steve Dark

steve-darkQuick Intelligence

When faced with a new database to analyse, and not much by way of requirement spec, I look to QlikView to help me profile the data and get feedback from the client. This is the one time I will use a SELECT * FROM in a load script, to pull all of the data from each table. Using the Export Table Structure feature in QlikView (File >> Table Viewer >> Export Structure) I can then get a good feel for what is in each table and share that with the business to get their feedback.

This makes it super easy for the client to decide which fields they ultimately want in their data model and also makes you look like a professional. You can see the full write up at Quick Intelligence.

Deepak Vadithala


Sometimes you need a listbox, but you want to hide the excluded values (the gray). My favorite tip is using aggr(FieldName,FieldName) as an expression for my listbox to exclude everything but the currently associated values.


Chandraish Sinha

chandraish-sinhaLearn All BI

To analyze the performance of a QlikView dashboard, visit Document Properties >> Sheets.
It will give you all the sheets created in the QlikView application. It will also give you the calculation time and memory utilization of each object within a sheet. You can analyze this information to improve performance of your QlikView application.
Analyze your QlikView Dashboard to Improve Performance

Julian Villafuerte


Uncover Qlik’s true power – QlikView and Qlik Sense are incredibly powerful platforms, so don’t settle for simplistic, out-of-the-box visualizations. With a little bit of imagination, a pivot table can become a heatmap and a boring bar chart can turn into a meaningful infographic. When you’re inspired, even mixing several text objects can create stunning results.

Oleg Troyansky

Oleg TroyanskyNatural Synergies

Excluding the Excluded. There are situations where after a user makes selections in one list box, we might want to limit the selections in another list box to the associated values, therefore excluding the excluded values. The easiest way to do that is to use a little set analysis. only({<Account=E({<Asset=E(Asset)>})>}  Account). A neat little trick. You can see the entire post at Natural Synergies.

Brian Booden

LinkedInBrian Booden

Paste Sheet Object as Link – I use this one all the time when templating out apps, especially ones that are heavy on common UI objects such listboxes, text boxes with images etc.  This method propagates changes across all linked objects.  Very useful when changing the field a listbox is attached to en masse, or the background image in a textbox across all sheets, for example.  You can access it by copying the object, then Right Click -> Paste Sheet Object as Link.

Miguel Angel Baeyens


Think in advance. Plan and think twice: Data modelling and performance are key for Qlik developments to succeed, and those factors need to be well set before the actual development.

Qlik development is creative. You need to understand the problem you are trying to solve. You have to understand why people will find Qlik useful and how it will save them time. You need to put yourself in the user’s shoes, ask yourself: what would you like to see? How would you like to use it? That will give you the key for a successful project, not just a well built one.

Rob Wunderlich

Rob WunderlichMasters Summit

QlikView Cookbook

I find that many developers don’t immediately think of using the Document Log for debugging script.  The log can be very useful, especially when using variables. Part of the reason some folks avoid the log is that it’s a hassle to get to. Wouldn’t it be nice if there were a toolbar button to open the log?  I add a button to all my documents that opens the Document log.

  1. Create a button.
  2. Add Action: External, Launch.  In the “Filename” parameter, add the expression:

=DocumentPath() & ‘.log’

QlikView Document Log Action

Clicking the button will open the log in the windows default program for “*.log” files. If you want to use a specific program, such as Sublime Text, you can enter that program in the Launch “Application” field.

This button can be Copy/Pasted to other QVWs without change as the logfile name is determined dynamically.

To prevent the button from showing in production (on the server, where it won’t work) I add a conditional Show on the button properties Layout tab:


Final Thoughts

Firstly, I was truly honored to interact with these experts. All were extremely willing and happy to participate and I thank them for their contributions and their greater contributions they make every day to our Qlik Community!

Get 9 More Tips from Our LinkedIn Audience.

LinkedIn Logo

We compiled even more tips from Qlik developers on LinkedIn. It was simply too much to include in one article, but you can gain access to these tips.

We never spam. NEVER.

As exceptional as this field of notables is, I really want to hear from you. What is your best QlikView Trick or Qlik Sense Tip? We are eager to hear it. Please add it to the comments. Thank you for supporting LivingQlik and for contributing to the greater Qlik community.


9 comments… add one
  • Reply Steve Dark November 8, 2016, 4:07 pm

    Thanks Aaron for including me amongst such awesome company. Some great tips here, and a good work done in compiling them.

  • Reply Aaron Couron November 8, 2016, 4:14 pm

    What I find interesting is that each tip seems to represent the unique personality of each contributor. Some are lengthy and detailed. Some are short and sweet. Some are philosophical. I was privileged to be a part of the process.

  • Reply Chris Troy November 9, 2016, 6:03 pm

    Hi, what does Adam Cooke mean by derive functions? Can you give a working example please?

  • Reply Aaron Couron November 10, 2016, 2:59 am

    Adam is finishing up a post now that will further detail his tip. We will add a link when he publishes it!

  • Reply Mike Schroff November 10, 2016, 10:44 pm

    When using Qlik Sense to help deploy business systems, I like to start my clients off with creating a sheet called “data profile” and make use of the embedded system fields $Field, $Table and $Rows to create 2 filter panes and ranked bar chart of Rows by Table. That helps the client to look through the actual data by filtering which gets them started on the actual mechanics of the software. That simple step helps clients to immediately experience the power of this wonderful platform.

    • Reply Aaron Couron November 11, 2016, 3:28 am

      Great tip Mike. It displays the power of the tool and drives the first project forward.

  • Reply Eva November 14, 2016, 12:39 am

    Thanks guys for sharing ! Many tips to get out of that.
    (“biggest names in the Qlik universe”… still no woman… not even 1 :'( )

  • Reply Aaron Couron November 14, 2016, 3:38 am

    Hi Eva,

    It was not for lack of trying. Three of the experts I reached out to happened to be female, but none replied to the request. If it helps at all, 3 of the 9 LinkedIn tips in the opt-in free content were from female contributors.


Leave a Comment

Join us at Living QlikView

Never miss a post.

We Never Spam. NEVER.

Show Buttons
Hide Buttons