One calendar or many calendars

[Alex1988]

Hi All, we have several fact tables in a schema.

This has meant we have created several calendars for each fact table. 

This is not great for a user as we need multiple linked slicers and so they have many date fields for different fact tables to choose from. 

What is best practice here? We have a subscription fact table with a start day and end date using 'use realtionship' function which makes it tricky to join these calendar tables together.

Is there anyway of making one slicer control and filter multiple date fields in different date tables?

Should I maybe be trying to avoid multiple fact tables? Should I use a bridge table?

My mind is boggled 🙂 

[Icey]

Hi @Alex1988 ,

Is this problem solved?

If it is solved, please always accept the replies making sense as solution to your question so that people who may have the same question can get the solution directly.

If not, please tell us exactly what you want and provide some sample data. This way we can help you more quickly and effectively.

Best Regards,

Icey

[amitchandak · Accepted solution]

@Alex1988 , You need to have one calendar as long as possible. Within the same table, you use relation to active inactive join. Which will be created when you create more than one join

refer

https://community.powerbi.com/t5/Community-Blog/HR-Analytics-Active-Employee-Hire-and-Termination-tr...

https://radacad.com/userelationship-or-role-playing-dimension-dealing-with-inactive-relationships-in...

But there is use case like cohort when you need to have two calendars.