Forum Discussion

Rbakker888's avatar
Rbakker888
Helper II
1 year ago
Solved

Relationship issues

Hi so I have an issue trying to link 2 tables together. The 2 tables I want to link are one about my orders and one about my hours which contains an orderID aswell for each hour entry. 

I need this cause I want to see the amount of hours I spend for each order. When I try to link it I get the following error tho:

The names of the tables I am trying to link are: fact_Melding which contains the orders and fact_Uren which contains the hours. dim_debiteuren is a table for my customers which is also linked to both but doesnt give me the right connection to work with. I need a direct connection from one table to the other.

 



  • Deku's avatar
    Deku
    1 year ago

    I am advising that you can't create that relationship. Can you create a dim_melting from the fields that can join to both of the tables, to provide the required filtering.

     

    If the join is for a specific measure, you can use CALAICLATE(...,USERELATIONSHIP()) to activate it for that measure. 

    Modelling will be the best option

6 Replies

  • Deku's avatar
    Deku
    Super User

    Can you share a images of the data model and indicate what type of relationship you are trying to create (i.e one many)

    • Rbakker888's avatar
      Rbakker888
      Helper II

      This is the relevant part of my database. The tables are linked by the following:
      Fact_Melding - Dim_Debiteuren: DebiteurId
      Fact_Uren - Dim_Debiteuren: DebiteurId
      Fact_Melding - Fact_Uren: MeldingId

      The last one is inactive as you can see but when I try turn it to active I get the error mentioned above. As the Fact_Melding is the table where this value is a unique value I am using a one to many relationship from there.

      • Deku's avatar
        Deku
        Super User

        If you were to turn it on, if you filtered Dim_Debiteuren there would be two paths to Fact_Uren. This would be ambiguous and is not allowed. Generally fact to fact dimensions are not recommended. I would advise trying to extract a commom dimension from Fact_Melding and Fact_Uren, and join it to both tables