> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/super-filter/features/10.-display-settings/ix.-no-data.md).

# ix. No Data

The **No Data** setting in Super Filter controls whether filter values are displayed by default or only after a user makes a selection. This feature is designed to improve visual clarity, enhance user focus, and optimize performance especially in scenarios where filters are intended to guide the user’s interaction before displaying data.

#### Configuration Steps

{% stepper %}
{% step %}
Open the **Format Pane** for the Super Filter visual.
{% endstep %}

{% step %}
Locate the **No Data** option under the relevant configuration section.
{% endstep %}

{% step %}
Enable the toggle to activate the feature.

* When **disabled** (default), the filter visual displays all available items even if no selection is made.
* When **enabled**, the visual remains empty until the user selects a filter value. No data will be shown initially.
  {% endstep %}

{% step %}
This option is supported across **all filter types**, including Hierarchy, Facet, Date, and Measure filters.
{% endstep %}
{% endstepper %}

<figure><img src="https://2237530339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPIvQSuyE40UC9wv5uGgW%2Fuploads%2FPvAOq37ICsJGQOGhzNqT%2FTreemap%20No%20Data.gif?alt=media&amp;token=b7ce5624-5659-486b-ac99-d6328fe0775b" alt="" width="563"><figcaption><p>GIF 1: No Data enabled using  Treemap Filter in dashboard.</p></figcaption></figure>

{% hint style="warning" %}
Note: This option was only available in Tree map filter. From version 5.6.0.0 it is available under **Display settings** in format pane.
{% endhint %}


---

# 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.inforiver.com/super-filter/features/10.-display-settings/ix.-no-data.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.