> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/supertables/guides/wildcard-search-in-any-group.md).

# Wildcard search in any group

When working with inline filters, a common requirement arises: enabling users to search across all levels within a hierarchical structure. In scenarios where there are multiple nested levels—such as the 15-level hierarchy in question—it becomes limiting when only one level can be filtered at a time, as shown in the current implementation.

A practical use case highlights this challenge: users might want to search for a specific term like "Person A" without needing to know which hierarchy level contains that value. Ideally, the filtering experience should be seamless and level-agnostic for the end user.

Below workbook contains an example that solves this challenge based on a Tableau Parameter and Tableau filter on the datasheet.

{% file src="/files/CI6xkVvymMo6eB3ezpPC" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/supertables/guides/wildcard-search-in-any-group.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.