one slicer: many date fields (or a suitable alternative)

[pmdci]

Hello,

I have a table in Power BI (a tabular model, SSAS on prem via Enterprise Gateway) that shows the targets for different service lines for each customer, based on a date.

The problem is that one of those targets (SLT5) is based on a different date field. So if I play with the slicer on the left, it will affect all columns except for SLT5. In fact SLT5 comes from a different fact table.

I wonder if there is a way to get one slicer that takes care of all all the columns?

The only way I see around this seems like too much hard work. Basically it would be for me to create a new table (a calculated table? will have to wait for SQL 2016) that has all the service level targets (SLTs) into them, and all of them are related to just one date field.

But I wonder i there is a better way?

Thank you for your time and support.

Regards,

P.

[Greg_Deckler · Accepted solution]

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.

[Greg_Deckler · Accepted solution]

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.

[pmdci · Accepted solution]

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.