Forum Discussion

Rik's avatar
Rik
Iron Contributor
Sep 10, 2025
Solved

Data product search is broken: no results for partial terms

Searching for data products using partial terms returns zero results, despite the existence of data products with matching names. For example, searching for 'risk' yields no results even though we ha...
  • Rik's avatar
    Jan 19, 2026

    The correct approach is for users to enable the “Search with natural language” option, which is located on the right-hand side of the interface.

    However, this behavior is not intuitive. I was unable to discover this option on my own, as the natural expectation is to enter a query and press Enter to initiate a search. The option only came to light when a colleague clicked it after typing a query, assuming it would start the search. Instead, the option disappears once text has been entered and must be selected before typing the query.

    This interaction pattern is confusing and easy to miss, which leads to unnecessary friction for users.

    I strongly recommend revisiting the UI/UX design of this functionality to make it more discoverable and aligned with standard user expectations. 

    Why is this option not the primary choice in the first place?

Resources