Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hello experts
Hi Experts
I am using a standard table in power bi from the screen image below the Agent Name is in the Rows field which filter perfectly when in add the pay zone ref from the second bridge table to the row field standard table - it does not filter down the data to pay zone level.
The agent name comes from Agent Bridge Table
The Payzone Ref comes from Pay zone Bridge Table
Both bridge tables have unique values.
Measure when using Agent Bridge Table
See image
second image to show data not filtering in end table
Solved! Go to Solution.
I can't read those screenshots. Can you take a screenshot with your computer instead of your phone's camera? The first one is so small I can't read any field.
To work around this issue, you would need to see the model. I suspect it's a field problem you're using in your cutter/filter, but I know all those two-way filters aren't helping things. Microsoft recommends minimizing the use of many-to-many, two-way relationships. In other words, unless you're a DAX expert, look for another way to reshape your data to fit a star schema and not use these two features. I avoid you both at all costs.
Microsoft's guidance on many-to-many relationships
Microsoft guidance on two-way relationships
Microsoft guidance on the importance of the star schema
How to get good help quickly. Help us help you.
How to get answers to your question quickly
How to provide sample data in the Power BI forum
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reportingmy measure for re-connected
I can't read those screenshots. Can you take a screenshot with your computer instead of your phone's camera? The first one is so small I can't read any field.
To work around this issue, you would need to see the model. I suspect it's a field problem you're using in your cutter/filter, but I know all those two-way filters aren't helping things. Microsoft recommends minimizing the use of many-to-many, two-way relationships. In other words, unless you're a DAX expert, look for another way to reshape your data to fit a star schema and not use these two features. I avoid you both at all costs.
Microsoft's guidance on many-to-many relationships
Microsoft guidance on two-way relationships
Microsoft guidance on the importance of the star schema
How to get good help quickly. Help us help you.
How to get answers to your question quickly
How to provide sample data in the Power BI forum
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingThank ill provide better screen shots shortly
See attached new image.... of models
Good afternoon/ evening to all power bi experts around the world
Any clues on how to resolve this lower level filtering issue?
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
111 | |
100 | |
80 | |
64 | |
58 |
User | Count |
---|---|
148 | |
111 | |
93 | |
84 | |
66 |