Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

encountering issue with synthetic key

Hi,

I am encountering issue while in data modeling.

i have time dimsion with the Date_key, i am trying to connect with the Date key into 3 Fact tables, those fact tables also have Date_key.

But the problem while  connecting more than 2 fact tables with the Date_key from time dimension, automatically Synthetic key is appearing with the table. is there any possiblities to avoid synthic key in Data modeling sheet and connect Date_key to 3 Fact tables.

4 Replies
Anonymous
Not applicable
Author

Hi Jaga,

Can u provide sample date.

R/Murali.

trdandamudi
Master II
Master II

You can keep the key field "Date_Key" in all the three tables and rename the remaining key fields if possible then it will get resolved. If not please share a sample app.

Example:

Fact1:

Date_Key

ID_Num as Fact1_ID_Num

Fact2:

Date_Key

ID_Num as Fact2_ID_Num

Fact3:

Date_Key

ID_Num as Fact3_ID_Num

shaktisinghchau
Contributor III
Contributor III

If possible remove/rename Date_ field in fact table otherwise best solution is to concatenate fields of composite key and make a single common field to join all the tables.

If you can share your table structure or QVW, will be able to guide you better.

Gysbert_Wassenaar
Partner - Champion III
Partner - Champion III

A synthetic key is not necessarily a problem. It may have no negative impact in your case. But we'll need more information about your data model to determine if that's the case or not. Can you post a small qlikview document that demonstrates the issue?


talk is cheap, supply exceeds demand