I joined a new project and am flabbergasted to see multiple DATE tables, connected to multiple FACT tables. The way business works is:
Fact tables:
Fact Sales Leads - All the leads are here.
Fact Sales Appointment - Facts related to Sales appts.
Fact Sales Job - Facts related to Sales job.
Date Tables:
Dim Date Lead Taken - They take the lead at a particular date.
Dim Date Appointment Set - This is appointment set date.
Dim Date Job Sold : Date when the job is sold.
My question is: Why do we need different date tables? I have never seen something like this. Am I missing something here, can it all be combined in 1 Date table?
Thanks,
i would try to use one date table EDNA Date Table that @Melissa has implements for the EDNA . Using three date tables would be a night mare.
First, I would find the first date and last date in each table make the table to include the first day of the fiscal year and last day for the fiscal year.
Thanks Keith. I convinced them to use 1 Dim Date table which will be connected to different fact tables but now the question is: if they want to know about for a particular lead, Lead Taken date, Appointment date and Job Sold date then how will they be getting data in 1 line for that?
if i remember correct you can a multiply 1 to many relationships but only one can be active at a time. Userrelationship i believe is the dax formula that you will have to use to active the other date.
you will have to review the course on the education portal.
