Star Schema: Multiple Dates

[ProudlyAnalytic]

Hello, everyone!

I am in the beginning stages of creating a large workbook that will contain more than ten tabs on the Report View. The data uploaded is well over 100K rows of data. (I cannot share any of the data due to privacy reasons.) Anyway, I come to you fine folks regarding the topic of MULTIPLE DATES. The three dates that will be used multiple times are: disbursement issue date, status date, and report date. Each tab will contain ONE visual with ONE of those three date columns.

On the Model View, I’ve begun arranging a star schema (better optimization for such a large workbook). I’d rather not go with the more data-heavy approach of creating one main calendar table (linked to the Fact table) followed by three separate calendar tables each one linked to a date (disb iss date, stat date and report date). I also don’t want to go with the other option which entails having some relationships inactive, I need all active relationships. Are there any other viable ideas before I go with the more data-heavy option? (The pic below details my notes for how the data-heavy option might look like in PBI.) 

I’ve scoured the internet, but cannot find the answer to my specific scenario, so I seek solace in this forum. I am fairly new when it comes to PBI, so please explain your suggestion like I am ten years old. I appreciate any advice received!

[ProudlyAnalytic]

Gotcha. Multiple date tables it is! Thanks for the confirmation, Deku! 🙂

(If anyone disagrees, please add your comment and reason for a healthy dialogue.)

[Deku · Accepted solution]

Nothing wrong with having multiple date tables. Particularly if you want to use more than one of then at a time, or don't want to over complicate measures. They tend to be quite small.

The advantage of a single date table is when you want to have measures that involve different date but have to be on the same access. For example order and sales dates. You want the count of sales to be on the date they sales occur and orders on the the day those occured. A common date table would be required in that case, with measures that involve userelationship() to activate a relationship