// troubleshooting guide · qlik sense
Qlik Sense Circular Reference & Synthetic Keys
- Status
- Workaround available
- platforms:
- Qlik Cloud, Qlik Sense Enterprise on Windows
- updated:
- November 18, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · qlik-sense/circular-references3 FIXES
// quick answer
Synthetic keys come from tables sharing more than one field; circular references come from loops. Build a composite key or rename shared fields.
Most likely fix: Rename shared fields
How to fix it
// try these in order, the most common fix is first
FIX 1Rename shared fields
- 01Decide which field is the key and rename the other duplicates with AS
Did this fix it?FIX 2Create a composite key
- 01Concatenate the fields into one key, for example with Autonumber, and drop the originals from one table
Did this fix it?FIX 3Remodel as a star schema
- 01Concatenate fact tables or use a link table for synthetic keys
Did this fix it?
SANDBOX · qlik-sense RUNS IN YOUR BROWSER
Try it: browse a sample shop and watch visitors, funnels and live data arrive
A hands-on Qlik Sense-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
A warning appears after load, the data model viewer shows dotted lines or $Syn tables.
Why it happens
- C-01Two tables share more than one common field
- C-02Tables linked in a loop
- C-03Data profiling auto-qualified shared field names
// this guide also covers
- qlik sense circular reference
- qlik sense synthetic key
- qlik sense synthetic key warning
Still not working?
If Qlik Sense keeps failing, you're not alone. See every Qlik Sense problem users report or the alternatives people switch to.
Done fighting Qlik Sense? Our small team builds your own Qlik Sense alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us