Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hy,
Please i need your help, to show me if this kind of relation is correct or bad
Thank for help
Looks to me as if you can improve this data model a lot by joining a bunch of those tables.
I am also missing a fact table if you are going for a star diagram.
Hi,
Without knowing the data it is quite hard to say. Ideally you should have a central fact table, the a snow flake schema from there.
Things to consider are
Can i join or concatenate the tables?
What is my fact table?
Hope this helps
Mark
If it worked and isn't too slow it's ok. - if not it should be transformed to a snowflake- or star-sheme. Are there any issues with this app?
- Marcus
Hey Kara,
You can join all the Absence tables to create a single fact table. Try to join these tables:
A little hint on to join them correctly:
You can make a key which you can know where the data are coming from like this: for exemple in the table Absence:
'Absence' as AbsenceType,
Hope it helps you
Regards,
MB
Thank for your answer,
my problem is that I have one table Personnel which contain all information about an employee and all other table have only Matricule_Personnel as key, so if i want to have an information about him i must link to Personnel table. I dont know what else
Are there any issues with this app? Joinning or mapping like suggested from MiguelBraga to get lesser tables would help to reduce the complexity. But before make sure that really all fields from these tables will be needed - the document analyzer will be helpful for this: Re: Document Analyzer V2 -- a major update.
Further noticeable is that there are no association to dates - if your datamodel only a big dimension table about staff it might not needed. Otherwise I would suggest to implement a master-calendar: How to use - Master-Calendar and Date-Values and this is probably helpful, too: Get started with developing qlik datamodels.
- Marcus
Thank you much Marcus Sommer, I will follow your instruction