We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
hi Does function all remove report level filter?
Do I Have to use allexcept to preserve that filter in measure and calculated columns?
Solved! Go to Solution.
Yes. Any filtering-type functions will return a single table. FILTER, SUMMARIZE, ALL, ALLEXCEPT, almost all of the time intelligence functions, ADDCOLUMNS, GENERATE, etc. etc. etc. If you're filtering two tables then you need two filtering functions, in this case two ALLEXCEPT functions.
The exception to this would be if you want to filter a single table based on a combination of conditions in that table and conditions in a related table. In that case you could nest ALLEXCEPT inside a FILTER and use RELATED to check a column in a related table. This only works in N:1 relationships, unless you want to get crazy with some combination of VALUES and RELATEDTABLE that I won't get into right now. Anyway, example:
Measure = CALCULATE( SUM(FactTable[NumberColumn]), FILTER( ALLEXCEPT( FactTable, FactTable[CategoryColumn] ), FactTable[ConditionColumn] = "foo" && RELATED(DimensionTable[StatusColumn]) = "xyzzy" ) )
Yes, and yes. ALL removes all filters including row context filters, visual level, page level, and report level filters. ALLEXCEPT(TableName, TableName[WhateverColumnIsInTheReportLevelFilter]) will preserve the report level filter but remove all other filters.
So when I want to preserve filters from two tables, I have to use allexcept twice
Yes. Any filtering-type functions will return a single table. FILTER, SUMMARIZE, ALL, ALLEXCEPT, almost all of the time intelligence functions, ADDCOLUMNS, GENERATE, etc. etc. etc. If you're filtering two tables then you need two filtering functions, in this case two ALLEXCEPT functions.
The exception to this would be if you want to filter a single table based on a combination of conditions in that table and conditions in a related table. In that case you could nest ALLEXCEPT inside a FILTER and use RELATED to check a column in a related table. This only works in N:1 relationships, unless you want to get crazy with some combination of VALUES and RELATEDTABLE that I won't get into right now. Anyway, example:
Measure = CALCULATE( SUM(FactTable[NumberColumn]), FILTER( ALLEXCEPT( FactTable, FactTable[CategoryColumn] ), FactTable[ConditionColumn] = "foo" && RELATED(DimensionTable[StatusColumn]) = "xyzzy" ) )
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 54 | |
| 39 | |
| 32 | |
| 17 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 63 | |
| 37 | |
| 34 | |
| 22 |