.svg){kind=icon}
.gif)
.svg)
- Login and open Qlik Sense App and click your app from the hub to launch it.
- Go to Prepare from the top menu, then open the Data load editor.
- Check your tables (for example, Region and Customers) and review fields that appear in both tables, such as Region and Region Code.
- In one of the tables, rename a duplicate field using AS (for example, Region as rg).
- Ensure only one field remains shared between the tables to act as the key (for example, keep Region Code as the common field and rename Region in one table), then click Load data.
- Open the Data Model Viewer to confirm no synthetic key table appears.
How to Avoid Synthetic Keys in Qlik Sense
Follow this interactive demo to learn how to avoid synthetic keys in Qlik sense.
📌 Why this matters
Why this matters
Avoiding synthetic keys from the start helps you maintain a clean and predictable data model in Qlik Sense. When multiple shared fields exist between tables, Qlik automatically creates synthetic keys that can lead to incorrect associations and confusing results. Preventing this at the scripting stage is much faster than fixing it later in a complex app. By controlling how fields are named and connected, you ensure accurate analysis, better performance, and easier maintenance as your data model grows.
Your product deserves an interactive demo
