# Filters

For example, a user can filter the Explore's query results to the last three months for a blockchain, or for a specific wallet address. Users can also limit the number of rows that are displayed in an "Explore" or the number of pivot columns that are displayed.&#x20;

### Filtering Data

Filters let you restrict the data that you are viewing to items of interest. Any field in your ChainArgos instance can become a filter.

You also don't need to add a "DIMENSION" or "MEASURE"  to your results to filter on it.&#x20;

For example, you can create a query that filters the "From Address" to the last three months, even though your results only show "Amount" and "Sum of Transfer Amounts."

You can use a **combination** of these filters in your query:

* **Basic Filters** are the most commonly used, and ChainArgos provides appropriate drop-down lists, widgets, and text fields.&#x20;
* **Advanced Filters** are highly customizable and allow user-configured specific values known as "user attributes" that allow a user to automatically customize a Look for each individual user (optional). Contact your system administrator if you would like to customize Advanced Filters for specific users in your workgroup.  &#x20;
* **Custom Filters** let you write the fields, constants, functions, and operators for your desired filtering. ChainArgos lets you build an expression that evaluates as `TRUE` or `FALSE`. When you run the query, ChainArgos only returns rows for which that condition is `TRUE`.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chainargos.com/documentation/concepts/filters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
