Forum Discussion
Advocate Vone slicer: many date fields (or a suitable alternative)
You could potentially just create a date table (or get one off of the Internet such as DateStream in the Azure Data Marketplace. Then just relate that date table to both of your fact tables based upon Date. Then you can use the date column from your date table in your slicer.
I already have a date table -- But you're right.
The solution would be to make a new copy of the date table and call it something like "Service Level Dates". I was brain dead yesterday and forgot that there are no relationship limitations when creating multiple relationships from one field in a fact table to different dimension tables (in this case, multiple date tables).
Regards,
P.
Community ChampionYou could potentially just create a date table (or get one off of the Internet such as DateStream in the Azure Data Marketplace. Then just relate that date table to both of your fact tables based upon Date. Then you can use the date column from your date table in your slicer.
Advocate VI already have a date table -- But you're right.
The solution would be to make a new copy of the date table and call it something like "Service Level Dates". I was brain dead yesterday and forgot that there are no relationship limitations when creating multiple relationships from one field in a fact table to different dimension tables (in this case, multiple date tables).
Regards,
P.