Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi folks,
I have been using parameter filter by binding it in Advanced option from Model, but whenever i am trying to do deselection after selecting all from a slicer or side panel filter, the deselection is turning into selection strangely, should I post this as an idea to Power BI product team or any one has a solution already in place?
Issue video: Deselection_issue_PBI.mp4
Issue image:
Also, attaching images along with above video and image links having high definition captures:
TIA,
rjgupta5757
Solved! Go to Solution.
Hi @kushanNa ,
Based on your explanation and the shared screenshots, it looks like you're encountering a known quirk in Power BI when using bound parameters with slicers—especially with the "Select All" and deselection behavior. The issue you're seeing, where deselecting an item ends up re-selecting it or resetting the selection altogether, often arises when the parameter is tied to dynamic M code or native SQL queries. This happens because Power BI re-evaluates the parameter whenever slicer selections change, and if your default value is set to something like "SelectAll", it can force the slicer to revert to that default when it loses context.
To address this, a better approach might be to avoid using "SelectAll" as a default and instead handle empty selections more gracefully by checking for null or empty lists in your M logic. You could also consider creating a simplified test file with just one slicer and one table to isolate whether the issue is visual or data model-related. If the issue persists even in the simplified version, it confirms that it's tied to how bound parameters behave during state transitions. And yes, if this functionality is critical to your report and disrupts usability, submitting it as a feature request to the Power BI Ideas portal would be a good move to bring attention to the product team.
Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.
Connect with me on LinkedIn: Rohit Kumar.
Hi @Pras678912,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please "Accept as Solution" and give a 'Kudos' so other members can easily find it.
Thank you,
Pavan.
Hi @rjgupta5757,
Since we haven't heard back from you yet, I'd like to confirm if you've successfully resolved this issue or if you need further help?
If you've already resolved the issue, you can mark the helpful reply as a "solution" so others know that the question has been answered and help other people in the community. Thank you again for your cooperation!
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you,
Tejaswi.
Hi @rjgupta5757,
Thank you for reaching out in Microsoft Community Forum.
Thank you @rohit1991 , @kushanNa for the helpful response.
As suggested by rohit1991,KushanNa., I hope this information was helpful. Please let me know if you have any further questions or you'd like to discuss this further. If this answers your question, please "Accept as Solution" and give it a 'Kudos' so others can find it easily.
Please continue using Microsoft community forum.
Regards,
Pavan.
Hi @kushanNa ,
Based on your explanation and the shared screenshots, it looks like you're encountering a known quirk in Power BI when using bound parameters with slicers—especially with the "Select All" and deselection behavior. The issue you're seeing, where deselecting an item ends up re-selecting it or resetting the selection altogether, often arises when the parameter is tied to dynamic M code or native SQL queries. This happens because Power BI re-evaluates the parameter whenever slicer selections change, and if your default value is set to something like "SelectAll", it can force the slicer to revert to that default when it loses context.
To address this, a better approach might be to avoid using "SelectAll" as a default and instead handle empty selections more gracefully by checking for null or empty lists in your M logic. You could also consider creating a simplified test file with just one slicer and one table to isolate whether the issue is visual or data model-related. If the issue persists even in the simplified version, it confirms that it's tied to how bound parameters behave during state transitions. And yes, if this functionality is critical to your report and disrupts usability, submitting it as a feature request to the Power BI Ideas portal would be a good move to bring attention to the product team.
Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.
Connect with me on LinkedIn: Rohit Kumar.
Hi @rjgupta5757
This is interesting. Maybe that column is used in another visual/page? Did you try creating a new file with just two visuals to keep it simple—one slicer using the selected column and another table showing the filtered data—just to confirm whether it's a visual-related issue or not?
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
84 | |
75 | |
68 | |
41 | |
35 |
User | Count |
---|---|
102 | |
56 | |
52 | |
46 | |
40 |