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 circular reference can be avoided?

Hi All

How circular reference can be avoided?

Regards,

Attitude

12 Replies
Not applicable
Author

kevin - yes it is true! but then you have to load the date dimension as many times as you have date keys in your facts - but never mind about it, i want to know what Link IDs are (mentioned by vinay).

hic
Former Employee
Former Employee

I think you should load the date dimension as many times as you have date keys. A query where you demand a specific ShippingMonth is never the same as if you demand the same month as ReleaseMonth, and the best way to make this difference obvious to a user is to have two different fields for the two.

See more on http://community.qlik.com/blogs/qlikviewdesignblog/2012/08/30/master-table-with-multiple-roles

HIC

Not applicable
Author

Hi,

one of possible solving of circular reference problem is (as was mentioned here) to rename and to add some new columns in one or more tables.

Take this example: You have three tables (T1, T2 a T3) and all of them has column key X, which you WANT to use for JOIN of them, but not like the CIRCLE but like the LINE: T1--->T2--->T3. Your target is to access T3 table from T1 table not directly, but indirectly - through T2 table.

So you will change your original definition of tables from this definition

1) T1 has one X column and other columns which are not important for us just now;

2) T2 has one X column and other columns...;

3) T3 has one X column and other columns...

to this new definition:

1) T1 has one renamed X column into X1_2 column and other columns...;

2) T2 has one renamed X column into X1_2 column, one new X2_3 column (with the same value) and other columns...;

3) T3 has one renamed X column into X2_3 column and other columns...

Regards,

Mirek