Why “It Works in the Chart” Is the Most Dangerous Sentence in Qlik Sense?

Read time: 2.5 minutes

5 Painful Realities About Chart Expressions Compared to Load Scripts

1️⃣ Chart Errors do Not Scale
Each new chart introduces the possibility of inconsistency if its logic is embedded.
To fix this, move reusable logic into the load script or master measure.

2️⃣ Recurring Expressions will create Issues
When you copy and paste expressions, they will gradually become inconsistent over time.
To fix this, standardize your Metrics with Master Measures.

3️⃣ Data Modelling is better than Visual Tricks
The purpose of an expression in a chart is to provide insights about the data and not to manipulate the way that data is presented in the charts.
To fix this, transform the data correctly when loading it into the model.

4️⃣ When Logic is in the Chart, Performance is Reduced
The performance of a dashboard will be reduced by having multiple heavy calculations in each visual.
To fix this, pre-calculate the fields whenever possible in the data model.

5️⃣ Governance Starts with Your Data Model
Trust can be lost without a central logic.
To fix this, create a good semantic layer in your data model before designing any visuals.

💡Key Takeaway: 

Quick fixes may provide a sense of accomplishment, but they do not lead to productive Qlik applications.

Instead of being based on the appearance of a diagram, as before, strong Qlik applications are developed from a clean model and a disciplined loading structure.