Relationship Structures

[Anonymous]

Hello,

I have many tables in a report. The tables are structured supposed to follow a star schema build.

Relationship structure:

All tables have Cross Filter Direction set to "both". The idea is to follow a star schema build. However, I am running into this issue:

I want the main table (gwp_forecast_master) to be the center of my star. But, I need time-smart relationships as well. So, I added a second "star" (Calendar) to center as the time intelligence table. Obviously, this ruins my star schema makeup.

I am a bit confused, and know I can do something better. I am running into all sorts of issues since only my main table can have an active relationship with the Calendar table directly.

Any tips/tricks/suggestions?

Thanks,

Joel

[v-shex-msft]

Hi @Anonymous,

I'd like to suggest you use the date function to manually define the calculated date ranges in your expression.
It does not require an additional calendar table and it can simply to customize and nested with other filters in DAX expressions. (time intelligence functions do not support these)

Time Intelligence "The Hard Way" (TITHW)  
Regards,

Xiaoxin Sheng

[PaulDBrown]

Having bi-directional relationships is not a good idea

[Anonymous]

I want my tables to be wise to the distributor relationships, as well as the dates of the data. So, how can I connect my tables so they are intelligent to both facets?