Forum Discussion

v-amarsh's avatar
v-amarsh
Microsoft Employee
5 years ago
Solved

Table relationship ambiguity

Hello Everyone,

I am facing an issue with the tables relationships.

I have below existing tables structure in my data model

Onwer, Location, Status, Scope, Assessment Phase, Planning Phase, Migration Phase (All these 7 tables are calculated tables using system and server table fields)----> Servers Table (1 to Many) with single filter direction
Onwer, Location, Status, Scope, Assessment Phase, Planning Phase, Migration Phase (All these 7 tables are calculated tables system and server table fields)----> Systems Table (1 to Many) with single filter direction

I get an error when trying to activate another main table SystemServers with existing System and Servers main tables

Below are the relationships I need to activate.

Systems to SystemServers using 1 to Many with single filter direction which works fine.
Servers to SystemServers using 1 to many with single filter direction, which throws below error

 

Relationships image:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

I cannot disturb any of the existing relationships as it would change my report design and filter behaviour.

Could anyone help please?

 

Thanks in advance !! 

3 Replies

  • Hi v-amarsh ,

     

    What is happening is that the cross filtering between tables is detecting that the relationship you want to use already exists but trough some intermidiate tables (not a direct connection).

     

    In this case depending on what you need to calculate you need to make use of the existing relations to make your calculations, using summarize or similar to create measures and get expected results, other option is to make use of USERELATIONSHIP, this will activate the inactive relationship when you want to calculate values between the two tables.

     

    https://docs.microsoft.com/en-us/dax/userelationship-function-dax

    • v-amarsh's avatar
      v-amarsh
      Microsoft Employee

      Hi MFelix,

      Thank you for the reply and solution. My problem is solved with the USERELATIONSHIP function.

      Also  LOOKUPVALUE function seems doing the same job as I've tested with this.

      Thanks

      Sharath Amarchinta

      • MFelix's avatar
        MFelix
        Super User

        Hi v-amarsh ,

         

        Don't forget to mark the correct answer.