Search Results without groups or filters

[Jason_Leffler]

The ability to return search results in any view (or dashboard) without being confined to an existing filter or group selection.

I'm finding it hard to navigate search results when I am using a collapsible group in a table view.  Say a user clicks on one of the groups to expand it, and uses the search bar, but the content they are looking for is in a different group.  The view returns no results, unless they know to click out of the group (collapse it) to return to the full group list.  This then shows the group that did return the results from the search.

The idea is some way to return results no matter where a user is or how they filtered a view

[Tijesuni]

You're facing a common issue in AppSheet where searching within a grouped or collapsed table view doesn't return results across all groups unless the user manually collapses the expanded group. Ideally, search should function globally across all data, regardless of grouping or filtering.

Possible Solutions & Workarounds:

1. Use a Slice for Global Search

• Create a Slice that includes all data and use that for a separate search-focused view.
• Users can switch to this "Search View" when needed, ensuring they see all results.

Steps:

1. Create a Slice (Data → Slices → New Slice)

In the Row Filter Condition, set:
TRUE

1.  (This ensures all rows are included)
2. Use this Slice for a separate Table View with search enabled.

2. Enable "Search Across All Data" in a New Table View

• Instead of relying on search within a grouped table, create a duplicate table view that does not use grouping.
• Place this in your Dashboard as a secondary view for better navigation.

3. Use a Quick Edit Search Field (Virtual Column)

If your users frequently search for specific fields, create a Virtual Column that combines searchable fields into one:

Add a Virtual Column:
CONCATENATE([Column1], " ", [Column2], " ", [Column3])

• Enable search on this column.

[Jason_Leffler]

@Tijesuni Thanks.  These are all things I already do as well to work around the issue.  This is why I posted it as a feature request.  Thank you for outlining the workarounds though!  I hope others find this helpful in the meantime.