Forum Discussion

yazenbarakat123's avatar
yazenbarakat123
Icon for Helper I rankHelper I
4 years ago
Solved

2 tables with Different dates

I have 2 tables , an Incident table and a Financials tables as shown below.    I'm trying to use these tables to create a Safety score  which is the  The Number of incidents that month / by the finan...
  • johnt75's avatar
    johnt75
    4 years ago

    No, you should link them on the Date field, so that it is a one-to-many relationship from Date to each of the other tables.

    You can make both relationships inactive, so as to not interfere with the current relationship, and then use USERELATIONSHIP in your calculations.

    It is not best practice to have many-to-many relationships, that can make for some very complicated DAX and some unexpected behaviours. It might be worth looking at changing your main relationship to one-to-many, possibly by building a bridge table between the two.

johnt75's avatar
johnt75
Icon for Super User rankSuper User
4 years ago

Create a proper Date table and link that to both of your existing tables. Use the Date table in your visuals and your calculations

  • yazenbarakat123's avatar
    yazenbarakat123
    Icon for Helper I rankHelper I
    4 years ago

    Thank you for your Qucik response ! however creating 2 relationships to a Date table will automatically disable on of the relationships , created a date table and connected them on the Month as seen below not sure if this is best practice 

     

    • johnt75's avatar
      johnt75
      Icon for Super User rankSuper User
      4 years ago

      No, you should link them on the Date field, so that it is a one-to-many relationship from Date to each of the other tables.

      You can make both relationships inactive, so as to not interfere with the current relationship, and then use USERELATIONSHIP in your calculations.

      It is not best practice to have many-to-many relationships, that can make for some very complicated DAX and some unexpected behaviours. It might be worth looking at changing your main relationship to one-to-many, possibly by building a bridge table between the two.