• Daily Success Snacks
  • Posts
  • “What’s a Synthetic Key?” — The Exact Moment Every Qlik Developer Ages 10 Years

“What’s a Synthetic Key?” — The Exact Moment Every Qlik Developer Ages 10 Years

Nothing unites BI teams faster than unexpected synthetic keys in production.

Author

Glenda Carnate
May 08, 2026

Read time: 2.5 minutes

“Wait… What is a synthetic key?"

The question may seem innocent enough to leadership, but it causes significant psychological stress for every Qlik Sense developer in attendance.

Initially, the app was functioning well. An extra field, with the same name as one already in the data model, was added.

This caused the Qlik Sense developer to be staring at the Data Model Diagram, feeling like it personally betrayed him/her, because of the following:

Odd associations, duplicate numbers, broken filters, and confused users.

How Synthetic Keys Cause Chaos!!

1. Shared Field Names Make Indirect Connections
Qlik makes connections between tables automatically.
SOLUTIONS: Structure Unique Keys Well.

2. Indirect Connections Can Conceal Problems with Logic
Typically occurred prior to the Data Connection.
SOLUTIONS: Clean and Normalize the Data Model before Hanging the Data Connection.

3. Additional Joins Do Not Represent Smarter Models
Added Complexity = Difficult to Maintain Approach
SOLUTIONS: Minimal & Functional Associations Only.

4. Poorly Structured Models Have No Trust
An incorrect KPI creates an immediate loss of confidence.
SOLUTIONS: Validate Associations prior to Publishing Applications.

5. Most Dashboard Problems Are Due to Data Model Issues
The visuals are not usually the problem.
SOLUTIONS: Data Model Development approved, like architecture, not configuration work.

💡Key Takeaway: 

Synthetic keys should not scare you because of Qlik, but rather they should scare you because they expose the messy logic of the underlying business.

When trust in a data source is lost, every dashboard will simply be "just a suggestion".

👉 LIKE this if synthetic keys have ever ruined your entire afternoon.

👉 SUBSCRIBE now to get relatable insights on Qlik Sense, BI chaos and enterprise analytics.

👉 Follow Glenda Carnate for sharp breakdowns of dashboards, data models and reporting reality.

👉 COMMENT "SYN KEY" if you have ever had to quickly pull up the data model viewer in a panic.

👉 SHARE this with your Qlik developer friends who are currently pretending that everything is under control.

Reply

or to participate.