Forum Discussion
Filter Order issue with TOP N usage
Apologies for the delay. I have reworked the visuals so this is no longer a problem, but have never actually solved why the visual had gone blank. Thank you for your attempts to help me though it is hugely appreciated!
Hi LYorkToenniges ,
Thanks for posting in Microsoft Fabric Community and for sharing the additional details.
I tested this with sample data where some rows have Adjusted Commitment as zero and others have valid values.
First, with a Bottom N filter on % Commitment only, the visual returns the lowest values including rows where Adjusted Commitment is zero:
After adding a filter to exclude zero Adjusted Commitment, the Bottom N recalculates and shows the expected result:
This confirms that in a clean dataset, the combination of Bottom N and the exclusion filter does not result in a blank visual.
If the visual is still blank in your case, please check if the Adjusted Commitment column is numeric and does not contain blanks, nulls, or text values that may be excluded differently.
Also verify if other filters such as Role = Production or page/report level filters are further restricting the dataset.
As a workaround, you can either create a calculated column that blanks out % Commitment when Adjusted Commitment is zero and then use that column in the Bottom N filter, or use a measure with RANKX that applies the exclusion before ranking so only valid rows are considered.
I am attaching a sample PBIX file with both approaches implemented so you can review the behavior directly.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi LYorkToenniges ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.
Apologies for the delay. I have reworked the visuals so this is no longer a problem, but have never actually solved why the visual had gone blank. Thank you for your attempts to help me though it is hugely appreciated!
Hi LYorkToenniges ,
Thanks for confirming.It’s good to hear that you were able to rework the visuals and move forward. Since the exact cause could not be reproduced with the sample data, the issue may have been related to a specific combination of filters or data conditions in your model. If you face a similar situation again, reviewing the Adjusted Commitment column for data type consistency and checking for any restrictive page or report filters would be good starting points.
Please reach out if you need further assistance.
Thank you.