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.
this has definetely earned you a new sub, you really nailed every part of the clarification needed throughout the tutorial. thanks a lot for this helpful tutorial. I have to learn from you a lot!
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 :)
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!
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 👍👍
"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.
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
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.
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
Such an important video. I keep seeing bi-directional relationships in model and model and my concerns usually fall on deaf ears. Great to have a very detailed video to point people to now. Something not discussed here but I thought I remembering seeing in the video training that SQLBI does - the bidirectional relationships can also slow performance because they tend to keep the model from being able to choose the optimal path.
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.
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 !
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 😊
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!
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.
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 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?
Beside limited cases (like implementing security patterns or physical implementation of M2M cardinality relationships - see sqlbits.com/Sessions/Event18/Different_types_of_many-to-many_relationships_in_Power_BI), it's almost never a good idea to enable bidirectional filters in the model, while it makes perfect sense in specific measure where you can control the side effects of it.
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/
Great, thx, great explanation... there are dax teachers who tell their students to put all the crossfilter in relations in both directions. Here is the reason why you never do this. Great alberto. ( who rides in a maserati! 😄)
Excellent video Alberto! Thank you very much. I'll send this link to all participants of my workshops and trainings! One question: What tool did you use to draw on your data model?
In this video am using Epic pen on the desktop, with Virtual tablet on the tablet, to use its pen. Worked ok... but not yet perfect, some lag and not as fluid as I'd like. In the next videos I stopped using Epic pen and I preferred to draw directly on the tablet, on top of screenshots. Much more fluid and much easier to use. Still searching for the perfect setup, anyway
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 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.
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?
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?
this has definetely earned you a new sub, you really nailed every part of the clarification needed throughout the tutorial. thanks a lot for this helpful tutorial. I have to learn from you a lot!
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 :)
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
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 👍👍
"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.
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 Mr. Ferrari, I love the way you raise the problem, analyze it and give the solution. Very clear and useful!
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.
This is a very neat trick to avoid ambiguity!! Thanks! SQLBI is on top of my top 5 resources!
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
Such an important video. I keep seeing bi-directional relationships in model and model and my concerns usually fall on deaf ears. Great to have a very detailed video to point people to now. Something not discussed here but I thought I remembering seeing in the video training that SQLBI does - the bidirectional relationships can also slow performance because they tend to keep the model from being able to choose the optimal path.
yes bidirectional filters can also affect performance, but first of all you need to get right numbers!
Excellent. So well explained. I would have never understood the consequences of bidirectional if I didn't bump into this video. Thanks a lot.
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 noticed the name of the final tab called "Welcome to hell" :D
Clearly explains the issue! Thanks for the content, very useful!
This is the best video I’ve ever seen on ambiguity and relationships. Thank you!
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 !
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 😊
Amazing explanation. Fixed the problem I didn't even know how to frame a question around.
What a good teacher you are, Alberto! Fantastic explanation! Tante grazie!
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..
Really Really Superb explanation, I love your videos .. one request if any monthly enable SQLBI its really helpful to me
I discovered the channel today and... congratulations on such quality content! Learning a lot here!
Sono rimasto stupefatto dalla chiarezza della spiegazione. Complimenti davvero
Really easy to understand, as always great job. Thank you SQLBI team for your amazing work.
You provided much better insight about bidirectional filter than Microsoft documentation / training.
Thank you very much for these videos Alberto and SQLBI! Learning a lot about DAX!
Amazing sir! The solution is so elegant that I have to clap when I saw it!
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.
Wow. I am taken aback by the explanation. Much love!
Hello Alberto. Have just found your channel. Awesome video. Just one request - pleaseeee do more examples on ambiguity. Really helps us the beginners.
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. 🤗
Excelente exposición!!! Eres lo máximo Alberto Ferrari.
This is a great! I need to try this next time I come across situation like this.
Thank you very much for these videos Alberto and SQLBI
Oh my goodness, such a beautiful explanation. Wow Man!
Fantastic explanation and presentation! Thank you so much.
I LOVE YOU Alberto !!
YOU ARE THE LEGEND
this video islike a movie of DAX !
Thanks! This quick solution of visual filters is possible only in Power Bi. In Excel, we use 'Crossfilter' in the measure formula.
This is a classic lesson. Thank you! Big up!
Cool. And yet so simple.
Love the sheet name “Welcome to hell” 😂
Literally busted out laughing when I saw that!
Excellent explanation! Congrats for such a great work!
So, the filter actually applies the crossfilter at the backend, this was not known to me , thanks a lot
Fantástico! Thank you MAESTRO!
Thank you a lot. Really happy to find this channel.
Love this one, a true best pratice that can change life and model design
Thank you for clear and precise explanation!
Nice explanation, i now finally understand ambiguity and now why i can not use bidrectional filters
Omg! Good problem, great explanation and excellent solution
Amazingly explained such a complex scenario.. Kudos!
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.
Thanks you to make it so clear and easy ! without avoiding to dig in detail :)
Make times fresher to me haha
Alberto is the "data monster"!
Absolutely perfect, thank you so much for this video
Ciao, friends! Enjoy DAX! Thanks for sharing
Mind blown! I need to try this. Thank you
Finally understood it right!!
Very insightful! Thanks for the knowledge master🙏
Holy crap I never would have thought of that in a million years! Thanks!!
Very well explained. Thanks Alberto.
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?
Great! Really really great examples and explanation!
This is very helpful, thanks!
Great Explanation Sir!! Keep it up👍
This is amazing, thank you so much for this video!
Wow. This is so informative and useful.
Very nicely explained. Thank you so much.
Very clear. Thanks!!
Really loved the tab you named "Welcome to Hell" 😀😀😀😀
Excellent Example of Crossfilter
Would've liked to see the "welcome to hell" calculated metrics before and after removing the both directions relationship.
Fantastic video!
I couldn't understand why filtering could make the data sync. Can you give me a simple example?
By the way, Great video, thanks a lot.
Useful content, poetic explanation...Suberb teacher
Great, thanks! Would be interesting if you have a video on when is a good time to use bi-directional relationships?
Beside limited cases (like implementing security patterns or physical implementation of M2M cardinality relationships - see sqlbits.com/Sessions/Event18/Different_types_of_many-to-many_relationships_in_Power_BI), it's almost never a good idea to enable bidirectional filters in the model, while it makes perfect sense in specific measure where you can control the side effects of it.
Great video, thanks!
Great explanation. You just earned a new sub sir.
This video is great but I'm not allowed to apply the measure on a visual if the visual is a card
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/
wonderful explanation... thank you...😀
awesome explanation, thank U
Your videos are amazing.
It's really cool. Thanks for sharing.
Such a nice explanation !!
Excellent Video! Thanks!
Great, thx, great explanation... there are dax teachers who tell their students to put all the crossfilter in relations in both directions. Here is the reason why you never do this. Great alberto. ( who rides in a maserati! 😄)
It hurts to know that someone promotes bad practices teaching that!
Excellent Video as Always!!
Grazie! Chiarissimo come sempre.
Excellent video Alberto! Thank you very much. I'll send this link to all participants of my workshops and trainings! One question: What tool did you use to draw on your data model?
In this video am using Epic pen on the desktop, with Virtual tablet on the tablet, to use its pen. Worked ok... but not yet perfect, some lag and not as fluid as I'd like. In the next videos I stopped using Epic pen and I preferred to draw directly on the tablet, on top of screenshots. Much more fluid and much easier to use. Still searching for the perfect setup, anyway
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 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.
thank you so much for this incridable video :)
Thanks for sharing...
Thank you for a great lesson
Thanks a ton for this
Great video
Excellent very useful