5 Brutal Truths Why Your “Single Source of Truth” in Qlik Sense Isn’t Single

Read time: 2.5 minutes

The Hard Harsh Reality Surrounding Your Qlik “Single Version of Truth”

1. 1 App ≠ 1 Definition
A single data set can represent multiple KPI’s, but when different logic is applied to the dataset, “Revenue” from one sheet may not always equal “Revenue” from another sheet.

Reality: Associations can be used to relate data together; however, they do not serve as a standard for defining the data.

Fix: Build an enterprise metrics layer which incorporates master measures and governed KPI definitions.

2. Apps Do Not Control User Behavior
Users export data from one application and then recreate calculations in Excel, leading to inconsistencies.

Reality: The source of information may be Qlik, but most of the time, the user will perceive that Excel is where to find it.

Fix: Use governed applications and limit KPI’s that are exportable to promote consistency.

3. Selection ≠ Consistency
The results obtained from applying different filters, alternate states, and vague fields can vary widely.

Reality: Flexible exploration creates Diversity of results.

Fix: Standardize Canonical Fields, Control Selections and Create Guided User Experiences.

4.  Logic is Not Centralized
Business Logic is scattered across the script, the UI and the sheets.

Reality: Fragmented business logic leads to duplicate business rules and incorrect results.

Fix: Centralized logic by utilizing the script for structure and the reusable measures for calculations.

5.  Qlik is Not the Truth
Qlik provides the Associative Layer… therefore, it is not a “Source of Truth”.

Reality: The definition of “Truth” is determined by the Data Model, Associations, and Definitions.

Fix: Create Separate Layers of Data Source, Data Model, Metrics, and Visualization.

💡Key Takeaway: 

The takeaway is that there is not one truth, but many truths based on how selections flow through a broken model.