Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hi,
I have a Problem. Ic have a Fact Table with data and IDs to other dimensions like in the picture. If I create two slicers with one domension as a filter each, I can filter the values in the Fact table, but I also want that the two slicers are filtering each other.
Is this possible? The dimensions are connected to the Fact table in a 1:n relationship and 1:1 relationship is not possible. Is there maybe a way to do it with parameters?
Thanks in advance! 🙂
Power BI can't handle many to many relations, if that is what you are asking. What can you tell about the key-column in DIM1 and DIM2? If they are unique and equivalent, you can make the connection.
Best,
Martin
Hi @Anonymous ,
the keys are not eqivalent. Imagine you have in the fact table the prices, in dim1 cars and in dim2 the years. So if I choose in dim1 a mercedes it would show years until 1926 and in the table the price for all cars since 1926, but if i choose Tesla it should filter the slicer with the years only until 2003.
Is this somehow possible without bidirectional filtering and joining tables?
especially on a live connection?
the other options is to denormalise the whole model @NerdFlanders
when you say live connection are you talkign sql server or sql server cubes?
Proud to be a Super User!
@NerdFlanders ah ok firstly can you actually alter relationships in the live connection? last i knew you couldn't
normalising would be summarising all the data into one table using the summarize function but once again, i am not up to date with the latest functionality in a live connection, i know its quite limited, if you need more flexibility and you aren't able to push back your requirement and do it in the source (the cube) then if its an option you might need to go the imported route.
however have you tried your hand at the lookup value function? however it is a bit of hard coding i think
Proud to be a Super User!
@NerdFlanders sorry unless i am missing something why is it not possible to do a bi directional relationship from the dims through the fact? dim to dim, that wouldn't make sense, otherwise it would be in one table, it goes via the fact
Proud to be a Super User!
@NerdFlanders have you tried changing your relationships to bidirectional? (ie set it to both not single)
Proud to be a Super User!
Hi @vanessafvg ,
as mentioned in the text a biderectional ( 1:1 ) relationship is not possible in this model.