Qlik Community

QlikView Scripting

Discussion Board for collaboration on QlikView Scripting.

Announcements
Coming your way, the Qlik Data Revolution Virtual Summit. October 27-29. REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Creator
Creator

Galaxy model (two fact tables, multiple dimensions)

Hi all,

I am trying to understand why this model does not work. I have two fact tables plus multiple dimensions (see image below). 

 

Circularreferences.PNG

 

Why i have this circular references when having unique keys?

Of course I could avoid that by concatenating these tables, but I need to understand why in Qlik having tow fact tables linked to the same dimension cause troubles.

Thank you in advance,

 

 

Labels (2)
5 Replies
Highlighted
Specialist
Specialist

Try to rename some keys in Fact tables in order to eliminate the Loop.

To help community find solutions, please don't forget to mark as correct.
Highlighted
MVP & Luminary
MVP & Luminary

I think this is the best explanation why it couldn't work: Circular-References 

- Marcus

Highlighted
Contributor
Contributor

There is not common fields between the two fact tables 🙂

 

If you have a closer look, you will see that each field in the fact tables has as a prefix the table name. I did that in order to avoid synthetic keys (qualify() function).

Thanks!

 

Highlighted
MVP & Luminary
MVP & Luminary

There are sensible usecases for qualifying - but linking fields respectively the reverse of avoiding them belong not them - this task should be always done explicitly.

Personally I would just concatenate the tables and if you need to know which values come from which source then add a source-field.

- Marcus

Highlighted
Digital Support
Digital Support

The issue is related to the circular reference post Marcus gave you, in your outlying tables you are calling from both fact tables, that is what is causing the reference, so you will have to kill that.  Pretty certain things are working as expected given the data model in this case.  Be sure to read over the Design Blog link Marcus posted earlier, that should help make sense of things, you have qualified things, but given those other tables are calling from both tables, that is what is creating the circular reference...  One of the engineers would have to explain things further, but if you fix that part of things in those other tables, that should stop things.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.