Forum Discussion
Standard table Second-level row field Not filtered.
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
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 schemaHow 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
6 Replies
- AnonymousNot applicable
my measure for re-connected
Re-Contracted = CALCULATE(COUNTROWS('STG Fact_To_Do_Closed'),'STG Fact_To_Do_Closed'[Task_Results] ="Resigned - New Agreement" ||'STG Fact_To_Do_Closed'[Task_Results] ="Resigned New Agreement – Terminal Ordered")if this helps - i might be missing something- edhans
Community Champion
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 schemaHow 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- AnonymousNot applicable
Thank ill provide better screen shots shortly