"disableFreeTextSearch" in si-filtered-search Not responding

[pragarthi-bits]

The disableFreeTextSearch parameter in the si-filtered-search-search-criteria component does not work as expected. Setting the parameter does not disable the free text search functionality.

Steps to Reproduce

• Use the si-filtered-search-search-criteria component.
• Set disableFreeTextSearch to true.
• Observe that the free text search input remains available/interactable.

Expected Behavior
When disableFreeTextSearch is set to true, the free text search input should be disabled, allowing users to filter only by the specified criteria.

Actual Behavior
Despite disableFreeTextSearch being set to true, the free text search remains enabled, and users can still input search terms freely.

[spliffone]

Even when free-text search is disabled, the input field should remain available if the component is editable. Disabling free-text should only affect the model and eventing—not the visibility of the input itself—as the field is necessary for users to filter dropdown criteria. Furthermore, clearing the entered text automatically when the dropdown closes creates a frustrating user experience, as it forces users to re-type their search if they didn't finish their selection.

Can you explain what is your particular problem with the behaviour?

[pragarthi-bits]

Based on my use case, users have a set of parameter filters to narrow down the data. Currently, the free text option allows users to type any kind of string for searching. However, our API only supports key-value searches, so we actually need to disable free text input entirely to avoid any confusion.

Right now, setting disablefreetextsearch only prevents the API call from being triggered, but the UI still allows users to type in the free text field, which can be misleading. Ideally, the free text input should also be disabled in the UI when this setting is enabled.

Refer image, we allow user to only search for "createdBy" parameter, and we provide set of value for it, not and independent value.

[panch1739]

Based on my use case, users have a set of parameter filters to narrow down the data. Currently, the free text option allows users to type any kind of string for searching. However, our API only supports key-value searches, so we actually need to disable free text input entirely to avoid any confusion.

Right now, setting disablefreetextsearch only prevents the API call from being triggered, but the UI still allows users to type in the free text field, which can be misleading. Ideally, the free text input should also be disabled in the UI when this setting is enabled.

Refer image, we allow user to only search for "createdBy" parameter, and we provide set of value for it, not and independent value.

Hello @pragarthi-bits !

Well, we cannot disabled the input because otherwise, users cannot type. Typing is required because the input serves two purposes: it captures values and it triggers the criteria search. Even when free text is not supported, the component still relies on user input to open and filter the list of available criteria. Disabling typing would prevent users from discovering and selecting those criteria.

If there is only a single criteria, the filtered search pattern may be unnecessary. This component is designed for discovering and combining multiple criteria through typing. When the criteria set is fixed, a simpler control like the si-select is usually more appropriate.