Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
omnipotamus
New Member

User Data Functions, List Slicer, and Select All

I have created a user data function that takes input from a list slicer, button slicer, and a text slicer. It creates a row in a SQL database for each item selected in the list slicer. This is working as expected.

 

However, if I try to use Select All in the list slicer, the button to submit becomes disabled with a message that something needs to be selected in the list (despite the fact that everything is selected in the list). I've found in searching that PBI treats select all as select none, which makes sense in other contexts, but not here. I've been trying to come up with a workaround, such as selecting all except one and then saving with that as the default state, but it's behaving unexpectedly.

 

Is there a way to use the list slicer with user data functions without the user having to select items one by one?

 

And/or, is there a way to use the list slicer with UDF and multiple fields in the list? The list stops showing up as an option for the data function when I add more than one field.

2 REPLIES 2
burakkaragoz
Community Champion
Community Champion

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.

Hi @omnipotamus ,
If the information posted by @burakkaragoz  is helpful, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post. If you are still facing any issue, please let us know in the comments. We are glad to help you.


We value your feedback, and it will help us to assist others who might have a similar query.

Thank you for your contribution in Fabric Community Forum.

Helpful resources

Announcements
June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.