Forum Discussion
See all rows in tabel visualisation
Anonymous - Well, it really shouldn't matter which one you choose. Keep the bridge table column and try changing those relationships to single direction versus Both.
Anonymous - OK, that's odd because I can see that the relationship exists between all those tables. Let's do a sanity check. How is your visual configured? You should be using the Bridge table's Cable Number in your visual and not the other Cable Number sitting in your other table.
Ahh... But I would like to show the data from the Cable Schedule to retrieve the RunAmp value from the load list.
Either way, I still got the same error message after changing it. I'm not quite sure why.
Anonymous - Without getting my hands on the PBIX I'm not sure how to troubleshoot.
Anonymous - Well, it really shouldn't matter which one you choose. Keep the bridge table column and try changing those relationships to single direction versus Both.
I managed to show the data after changing the RunAmp from "don't summarise" to sum however, the data set is being repeated for every single row which I can't seem to understand why.
Anonymous - Do you need to switch a Don't Summarize on like Description to First or something?
Apologies, I don't quite understand what you mean.
Did you mean this? Or is there something else I should change?
Anonymous - Yes, that's what I was referring to.
I tried all of it and it can't seem to work I get the number being printed out repeatedly multiple times.
The odd thing is I reopened my original file when the relationship was many-to-many (despite the bridge built through DAX saying all the values are distinct) which was not ideal and it surprisingly works now. Tried to build the bridge table in the query to get a 1-* relationship again and I get the issue of the item being printed multiple times for every single row.
I am quite confused on what I should do; to fix the relationship and get that right or leave it as many-to-many as long as I get to see the data I want (not sure if I will get issues in the future).
Thanks in advanced for your help