Forum Discussion
Relationship issues
- 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
Can you share a images of the data model and indicate what type of relationship you are trying to create (i.e one many)
- Rbakker8881 year agoHelper 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.- Deku1 year agoSuper 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
- Rbakker8881 year agoHelper II
I dont really understand how you advise me to join it to both tables cause when I try it doesnt allow it due to the same reason. Providing a bigger part of my model could you possibly provide a more specific answer?
I am aware I cannot edit it in this file btw