-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not filtering data properly #42
Comments
Hello @dittmk, |
Thanks Uve. How does this slicer get tested with Power BI upgrades? How do you know that you can trust that the selector will be function? We're driving a business based on this - all the way up to my C-level staff... need to ensure that what we have is working properly & when it's not - there needs to be notifications of that rather than having my C-level staff tell me it isn't (which is what happened in this case...) |
Having the same problem! |
Same problem here. The visual works well in Power BI Desktop, but it's not working in a published report (web view). Actually the user needs to update the view to reflect the selection change, which is annoying. |
I have a new issue with this slicer - which I love, btw.
We have a Yes/No toggle using this slicer on 100% of our reports currently. No is the default value. It had been working beautifully until 10/23 when the users began to report to me that when they click Yes - all that happens is that the "Yes" side of the toggle is selected. The data on the report does not change. Then when they click "No" - the toggle changes & the data changes to reflect the "Yes" data set. This is causing chaos in our reporting and I am removing the chicklet slicer in a matter of minutes to ensure the data is correct.
On the powerbi store - I have seen a few other comments along these lines - that the slicer does not select the correct data. Wanted to make sure you were seeing these things.
If there is a way I can be of assistance in resolving this - please do let me know. I would much prefer this option rather than the check-box that I am moving back to.
The text was updated successfully, but these errors were encountered: