The Zurich release has arrived! Interested in new features and functionalities? Click here for more

How to Toggle All Options in List Selector Inside Repeater When "All" Is Selected in UI Builder?

OscarZ
Tera Expert

Hi everyone, I'm working on a use case in UI Builder for a workspace experience, and I need help implementing a toggle behavior for a list selector inside a repeater.

Setup:

  • I have a left column that contains a repeater.

  • Inside the repeater, there's a list selector for each category.

  • The options for each list selector are generated via a script.

  • We're using Client State Parameters (CSP) to pass the selected values to various data visualizations.

What I’ve done:

  • I added a new option called "All" to each list selector.

  • The CSP updates correctly when selections change.


The challenge: I want the "All" option to behave like a toggle:

 

  • When "All" is selected, all other options in the list selector component should be selected automatically.

  • When "All" is unselected, all other options should be unselected as well.

I’ve tried using a client script to emit a custom event and manipulate the selection, but I haven’t been able to get the list selector to update correctly — especially within the repeater context.

Goal: Implement a behavior where:

  • Selecting "All" selects every option in the list.

  • Unselecting "All" clears all selections.

Has anyone implemented this kind of toggle logic inside a repeater? Any tips on how to programmatically update the list selector’s selected values or trigger a re-render?

Thanks in advance for any help or ideas!

 

 



 

 

1 ACCEPTED SOLUTION

OscarZ
Tera Expert

Yes, the issue has been resolved. The root cause was the specific component we were using. We initially had a list selector inside the repeater, but it wasn't functioning correctly in that context. Replacing it with a dropdown component within the repeater resolved the problem. Updating the component to one that works properly within the repeater context was the key fix.

View solution in original post

5 REPLIES 5

OscarZ
Tera Expert

Yes, the issue has been resolved. The root cause was the specific component we were using. We initially had a list selector inside the repeater, but it wasn't functioning correctly in that context. Replacing it with a dropdown component within the repeater resolved the problem. Updating the component to one that works properly within the repeater context was the key fix.