Bidirectional relationships and ambiguity
HTML-код
- Опубликовано: 9 июл 2024
- Learn how to avoid ambiguity caused by bidirectional relationships in a Tabular model with Power BI or Analysis Services.
Article and download: sql.bi/75696?aff=yt
How to learn DAX: www.sqlbi.com/guides/dax/?aff=yt
The definitive guide to DAX: www.sqlbi.com/books/the-defin... 
Наука
Brutal! I spent 4 sleepless nights because of that... thank you so much!
I can't even begin to describe how happy I am that i found this video. I was about to redesign my whole model to only use one fact table, and all I had to do to get the filters to sync was add a measure. Thank you so much! Great video.
Hi, Would you mind sharing more please? What type of measure did you create to get the filters to sync please?
Thank you Mr. Ferrari, I love the way you raise the problem, analyze it and give the solution. Very clear and useful!
"Welcome to Hell!" I was laughing so much that I had to pause the video to put in this comment! I think the real key to understand why adding the filter to the slicer works is that a slicer is just another visual. All the usual cross-visual filtering rules apply. It's one of those things that is obvious if you think about it at all, but it is easy to fall into the trap of thinking a slicer is just a different way to show a filter. I did.
I noticed the name of the final tab called "Welcome to hell" :D
Clearly explains the issue! Thanks for the content, very useful!
man wow, how beautifully he explains and all the tools he uses. a true master.
could you please help me in understanding why it worked after applying the visual filter?
in Summation WOW -- the really explains why you should ALMOST never use bi-directional relationships for purposes of filtering and why you probably should ALMOST NEVER trust a model that does .. in the back of my mind I was trying to figure out how the ambiguity impact things -- great walk through THANK YOU
My company created a bunch of data models where every possible relationship is bi-directional before hiring me...
I told them that I won't touch them and I won't take responsibility for the numbers they display and your video will be a very good example why you need people who knows how to build data models as it's not simply drag and drop.
Thank you very much for a very informative and well presented video :)
While looking for a solution for my model that has a lot of bidirectional relationships, I meet Alberto with the amazing video and the answer for my big question. Thank you for your great works, I always appreciate your contribution to make DAX easier to use
Thank you for this clear explanation (love the handwritten arrows on top of the modeling view !). Aside from the ambiguity arising from the use of a bidirectional relationship (which I manage to keep away from), I discovered a neat way to show only relevant choices in slicers !
This is the best video I’ve ever seen on ambiguity and relationships. Thank you!
Really easy to understand, as always great job. Thank you SQLBI team for your amazing work.
This is a very neat trick to avoid ambiguity!! Thanks! SQLBI is on top of my top 5 resources!
Excellent. So well explained. I would have never understood the consequences of bidirectional if I didn't bump into this video. Thanks a lot.
Just as I was looking at this, I found this video and it answered everything. Thanks Alberto.
I think PBI should give a warning if it detects alternate fllter paths.
If it would be difficult to explain such ambiguity to a non-technical person, then the design should be changed. The stakeholders/consumers will lose trust and confidence if something is happening that cannot be understood.
What a good teacher you are, Alberto! Fantastic explanation! Tante grazie!
Amazing explanation. Self service BI report developers MUST watch this video. I had to explain this to lot of people and now I can just guide them here 👍 Thank you.
I discovered the channel today and... congratulations on such quality content! Learning a lot here!
Thank you very much for these videos Alberto and SQLBI! Learning a lot about DAX!
Amazing explanation. Fixed the problem I didn't even know how to frame a question around.
Thank you so much Sir for posting this valuable video. I can't express my gratitude towards you that how much I was needed this video.
Thank you again 😊
I LOVE YOU Alberto !!
YOU ARE THE LEGEND
This is a classic lesson. Thank you! Big up!
Awesome! I am working on a model and I am happy I found this.
Fantástico! Thank you MAESTRO!
Thank you a lot. Really happy to find this channel.
I always had issues with ambiguous models. and what I concluded from my report is to never use bi directional filter. I never knew what was the reason.
now I got
I must appreciate your efforts 👍👍
Excelente exposición!!! Eres lo máximo Alberto Ferrari.
Fantastic explanation and presentation! Thank you so much.
Mind blown! I need to try this. Thank you
Thank you Alberto i have been looking at that trick for weeks since i have similar business problem. Glad i came a croos the video. 🤗
Wow. I am taken aback by the explanation. Much love!
Thank you very much for these videos Alberto and SQLBI
Absolutely perfect, thank you so much for this video
Thank you for clear and precise explanation!
Excellent explanation! Congrats for such a great work!
Very insightful! Thanks for the knowledge master🙏
You provided much better insight about bidirectional filter than Microsoft documentation / training.
Love this one, a true best pratice that can change life and model design
Excellent Video as Always!!
Really loved the tab you named "Welcome to Hell" 😀😀😀😀
Amazingly explained such a complex scenario.. Kudos!
Amazing sir! The solution is so elegant that I have to clap when I saw it!
This is amazing, thank you so much for this video!
Excellent Video! Thanks!
Wow. This is so informative and useful.
Very well explained. Thanks Alberto.
Very nicely explained. Thank you so much.
Great! Really really great examples and explanation!
Great video, very clear and well done, thanks Mr. Ferrari. I would just emphasise that that the problem presented doesn't come only from using the bidirectional relationship, but it comes form using the bidirectional relationship IN a loop, because in a purely star schema no ambiguity is created when using bidirectional relationships. This would be just to reinforce what is already a great explanation!
True - but you have to be sure you'll not add other fact tables to the same model sharing the same dimensions... in the future
Oh my goodness, such a beautiful explanation. Wow Man!
Your videos are amazing.
This is very helpful, thanks!
Grazie! Chiarissimo come sempre.
Finally understood it right!!
Very clear. Thanks!!
This is a great! I need to try this next time I come across situation like this.
Great video, thanks!
It's really cool. Thanks for sharing.
Fantastic video!
Such a nice explanation !!
Thanks you to make it so clear and easy ! without avoiding to dig in detail :)
Make times fresher to me haha
Omg! Good problem, great explanation and excellent solution
Thank you for a great lesson
Very elegantly explained. Using the side Filter Pane would not have occured to me. I would have edited the Sales Measure by using CROSSFILTER. But I think the Filter Pane, does the job just as well!
yes, but you have to do anyway the 'trick of filter pane' if you want to "synchronize" the two slicers...so two birds with one stone..
awesome explanation, thank U
Great explanation. You just earned a new sub sir.
Thanks a ton for this
Nice explanation, i now finally understand ambiguity and now why i can not use bidrectional filters
well explained. Thank you.
Excellent Example of Crossfilter
wonderful explanation... thank you...😀
Really Really Superb explanation, I love your videos .. one request if any monthly enable SQLBI its really helpful to me
I was facing the same issue and was stuck trying to figure out how bidirectional works from the last 2 days. I tried to check if it works like sql joins but still the result was ambiguous showing a greater value than that in sql. Thanks a lot for making this content. For slicer u used 'is not blank' filter. but i have direct column from 2 unrelated table(not connected directly, although connected through other tables, but flow non-unidirectional) and that too numerical(sum of amount). But now i hope i will figure it out how is it working in my case. thanks a lot lot sir. its much much informative and helpful.
thank you so much for this incridable video :)
Thanks! This quick solution of visual filters is possible only in Power Bi. In Excel, we use 'Crossfilter' in the measure formula.
Alberto is the "data monster"!
Great stuff 👍
Hello Alberto. Have just found your channel. Awesome video. Just one request - pleaseeee do more examples on ambiguity. Really helps us the beginners.
Useful content, poetic explanation...Suberb teacher
Very, very well explained!
*standing applause
Great video
Cool. And yet so simple.
Love the sheet name “Welcome to hell” 😂
Literally busted out laughing when I saw that!
Hello Alberto, thanks for putting this video together. Very helpful!
I do have a question about the sales measure you used and the calculation it performs. Would you be able to share?
Thank you for providing this detailed video on ambiguous models. There isn't a lot of information out there, so this is very much appreciated.
Though, I only see a problem if you have a model with two fact tables. If you keep things simple (single fact table, multiple dimension tables), there should be no opportunity for multiple paths, correct? Therefore the model wouldn't be ambiguous?
Thanks for explaining this, much appreciated.
Alberto, can you read this thread on the same topic. If you have any thoughts please comment.
www.reddit.com/r/PowerBI/comments/kqsy0v/filter_direction/
Thanks for all the insight you have been sharing.
You should avoid bidirectional filters in the model, use them in the measures only if possible.
Best practices, workarounds, and explanations here:
www.sqlbi.com/articles/syncing-slicers-in-power-bi/
www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/
Thanks for sharing...
Thank you Alberto 🇮🇹🇮🇹🇮🇹
Ciao, friends! Enjoy DAX! Thanks for sharing
Holy crap I never would have thought of that in a million years! Thanks!!
This video is great but I'm not allowed to apply the measure on a visual if the visual is a card
Excellent very useful
AMAZING! THANKS
great! thanx!
thank you so much for this video. It was of great help. What if the "Color" is not in the slicer but in the visual and the user wants the visual filtered based on selection in "customer" slicer? how do i achieve that?
Hi Alberto. I think it would stand to reason to also mention that if someone uses USERELATIONSHIP and/or CROSSFILTER, they should always make sure that such a manipulation does not transforms the model into an ambiguous one.
Thank you for a great video. I'm a newbie and am a bit confused as to how the direction of filtering goes when you apply a filter on the visual in the end of the video. It seems the cross filter direction does not affect that, since a filter on sales has an effect on product.
Thanks a ton for the great explanation!! I tried it out and worked perfectly! However, if I want to influence from lets say the customer dimension, a measure in the products table, then this does not seem to work. Would you be so kind to help?
Good video.Actually what happen in the behind when you add sales measure to the filters as not blank.Can you elaborate?
Would've liked to see the "welcome to hell" calculated metrics before and after removing the both directions relationship.