Table widget allows user to create filters using hidden fields

[DHCDAnalysis2]

I have several fields in my layers hidden because I don't want my users to see them, but they are totally exposed in the "set filter" action of the Table widget, even the ObjectID field! Why would I ever want the user to be able to filter based on ObjectID? I've tried setting these fields to hidden in Pro before even publishing, in my web map, and in the table widget settings, and none of these settings are respected by the filter function. Am I missing something?

[Shen_Zhang]

Hello @DHCDAnalysis2,

Thank you for sharing this feedback.

The Set Filter data action is a framework-level capability that is designed to work consistently across all widgets (such as the Table, List, and Feature Info widgets). Because of this, it always exposes all fields in the layer, regardless of visibility settings that may be applied in Pro, in the web map, or within individual widget configurations.

At the moment, the Set Filter action does not respect hidden field settings, as it is intended to provide a complete set of filtering options at the data level. I understand that this may not align with every workflow, and if your goal is to restrict what users can see or filter on, one possible workaround is to publish a view layer that excludes sensitive fields entirely. This ensures they’re never exposed through filters or other widgets.

[TimDe_Muynck]

Is it possible to see any improvement in this in the future? We are struggling with this as well. It would be convenient if the option simply existed within Experience without having to work with View Layers. Thanks