Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

How many ways to avoid the synthetic keys ?

How many ways to avoid the synthetic keys ?

5 Replies
Not applicable
Author

Countless! Depends on the problem, but there's no only one, two or three ways.

rbecher
MVP
MVP

Hi Naveen,

the most common ways IMHO are:

- building compound key fields (concat the values with a delimiter: field1 & '_' & field2)

- use link tables with distinct occurances of the field combination and use autonumber as surrogate key

- join the two tables to one resulting table

- Ralf

Astrato.io Head of R&D
Clever_Anjos
Employee
Employee

Ralf Becher covered 99% of the situation

MayilVahanan

HI

With addition of Ralf Becher ,

You can also  rename the fieldname to avoid synthetic key

Thanks & Regards, Mayil Vahanan R
Please close the thread by marking correct answer & give likes if you like the post.
v_iyyappan
Specialist
Specialist

Hi,

To remove the Synthetic Key to use following method,

1. When any two tables share more than one common field, QlikView creates a complex key, or synthetic key, to try and associate both tables through the combination of all of the common fields between them.

2. This takes the form of an additional table containing the shared fields and an additional key field added to all involved tables.

3. Suppose tables all filednames same means use the concatenate function to remove the Synthetic Key

Regards,