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: 
Anubis07
Contributor
Contributor

Data Model

Hello everyone, 

Can anyone help me finding the best way to create a data model for an app. The App has 3 Fact Tables. All are now separately connected to the ClientData Table. What i need is to connect them somehow to a MasterCalendar to have a common date field in the App..

These are the connections i need. But i would fall into a Loop with the following Data Model. 

Anubis07_0-1728999016067.png

Does anyone has a suggestion on how should i create a data model, so that the app is smoothly running. 🙂

Labels (1)
1 Solution

Accepted Solutions
marcus_sommer

Within the most scenarios it's possible (and usually the simplest method) to concatenate the fact-tables - ideally by harmonizing all field-names and data-structures as much as possible.

Your screenshot of the existing/intended tables looked not really suitable because it tried to connect a redundant as-of-facts with a as-of-table and on it the calendar. The facts should be rather regular and are connected with the calendar and parallele is also the as-of-table or they is then connected as satellite to the calendar. 

View solution in original post

3 Replies
mpc
Partner Ambassador
Partner Ambassador

Hi, 

A common way to resolve this when multiple fact tables are involved is to concatenate them.
You only need to have the same Calendar field in each table. Null value matrix are not a problem for Qlik Engine. 

Kind regards 

From Next Decision and mpc with love
Anubis07
Contributor
Contributor
Author

Hi mpc,

Thank you very much for the quick answer. I have thought about concatenating them by using same Periode field, but the client data cannot be always same in all 3 fact tables... and when i concatenate the tables i cannot connect it to client table based on 3 client keys..

marcus_sommer

Within the most scenarios it's possible (and usually the simplest method) to concatenate the fact-tables - ideally by harmonizing all field-names and data-structures as much as possible.

Your screenshot of the existing/intended tables looked not really suitable because it tried to connect a redundant as-of-facts with a as-of-table and on it the calendar. The facts should be rather regular and are connected with the calendar and parallele is also the as-of-table or they is then connected as satellite to the calendar.