Inconvenient behavior when placing a Choice field in UI Builder list filters

[mugi-san]

Hello, Everyone.

I created a workspace using UI Builder and placed a list component.

I then configured a default filter to restrict the records by a specific Choice field.

However, when list filters are enabled and the Choice field is displayed on the list,

users are still able to select choices outside of the ones filtered by the default filter.

I am looking for a workaround or method to restrict the selectable options displayed in the filter.

Does anyone know a better way to do this? Other than hiding the Choice field from the list and using a separate component/event as a filter, or just creating a new field on the table side to display it.

P.S. For this field, I am assuming the sys_class_name field.

Regards,

[Vikram Reddy · Accepted solution]

Hello @mugi-san,

I'm assuming you turned on the built-in column filter/sort on the List component itself, with your default filter set on the Data Resource condition behind it. That's the root of it: UI Builder pulls the filter's choice options straight from the field's full choice set across base and extended tables, completely independent of whatever default filter or condition you've applied. It's a platform limitation rather than something you've misconfigured, and it's especially visible on sys_class_name since its values come from the class hierarchy in sys_db_object rather than a scoped choice list. A few things worth checking before you write it off:

• The Configure values option on the filter setup, some list configurations let you hand-pick the subset of choices shown instead of pulling every one
• Whether your List component's filter config exposes a per-column toggle, so filtering can be turned off for just that Choice field instead of the whole list
• Logging it as an enhancement request if neither pans out, this exact gap keeps coming up on the Next Experience forum with no clean fix yet

Thank you,
Vikram Karety
Octigo Solutions INC