Forum Discussion
User Data Functions, List Slicer, and Select All
Hi omnipotamus ,
Yeah, this is a known quirk with list slicers and user data functions in Power BI. When you hit "Select All," Power BI actually treats it as “none selected” in the backend, which breaks UDF submission (the button gets disabled). There’s no native fix—users have to manually pick items.
Workarounds people use:
- Tell users to select all items manually (not ideal, I know).
- Sometimes you can pre-select all but one, save that as default, and instruct users to add the last one, but it’s clunky.
- No way right now to use "Select All" and have it behave as expected with UDFs.
For your second question:
If you add multiple fields to the list slicer, it stops supporting UDFs—this is also a current limitation. Only one field in the slicer works with user data functions.Not perfect, but that’s the state of things. If you want, you can add an idea in the Power BI forums for better support!
Let me know if you want help with any specific workaround.
translation and formatting supported by AI
Hi omnipotamus
Just checking in to see if you had a chance to review the response shared earlier by burakkaragoz regarding your question on using list slicers with user data functions.
If the solution was helpful, please consider marking it as the Accepted Answer this helps others in the community who may be facing similar challenges.
If you still have any questions or need further assistance, feel free to reach out we’re here to help!
Thank you for being part of the Microsoft Fabric Community!
Hi omnipotamus
I wanted to follow up on your question regarding the user data function and the behavior of the list slicer in Power BI. It seems that the issue with the button being disabled when using the "Select All" option is a known limitation, as Power BI treats "Select All" as "Select None" in certain contexts.
To work around this, you might consider implementing a default selection that includes all but one item, as you mentioned. However, if that approach is not yielding the expected results, here are a couple of suggestions:
- Custom DAX Measure: Create a DAX measure that checks if the "Select All" option is active and returns a value that allows the button to remain enabled.
- Alternative Slicer: Consider using a different slicer type, such as a dropdown or a multi-select slicer, which may handle the "Select All" functionality differently.
Regarding your second question about using the list slicer with multiple fields, Power BI currently has limitations on how many fields can be included in a single slicer for user data functions. If you need to use multiple fields, you may need to create a combined field in your data model that concatenates the values of the fields you want to include.
If these suggestions help resolve your issue, please consider marking this response as the Accepted Answer. This will assist others in the community who may face similar challenges.
If you have any further questions or need additional assistance, please don’t hesitate to reach out. We’re here to help!
Thank you for being an active member of the Power BI Community!