> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/filtering-and-sorting-data.md).

# Filtering and Sorting Data

Filter rows and sort results to focus reviews and standardize repeatable lists.

### Overview

Filters narrow a view to a relevant dataset. Sorting controls review order inside the dataset.

Filters and sorting are typically stored with the current view configuration.

{% hint style="info" %}
Screenshot placeholder: List View toolbar with Filter and Sort controls highlighted.
{% endhint %}

### Key Concepts

* **Filter**: rule that includes or excludes rows
* **Sort**: ordering rule for rows
* **Save View**: stored configuration for repeatable filtering and sorting

### How It’s Used

Use filters to build repeatable review lists. Use sorting to establish a stable review order.

### Benefits

* Cleaner daily review lists
* More consistent triage and reporting

### Setup Steps

#### Filter rows

Filters narrow the dataset shown in the view.

{% stepper %}
{% step %}

#### Open filters

Click **Filter** in the view toolbar.
{% endstep %}

{% step %}

#### Add a filter

Click **Add filter**.

Choose a field and a condition.
{% endstep %}

{% step %}

#### Combine filters

Add multiple filters for a tighter view.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Screenshot placeholder: filter builder showing 2–3 filters and the filtered table results.
{% endhint %}

{% hint style="info" %}
GIF placeholder: add a Status filter, then add an Assignee filter, then clear one filter.
{% endhint %}

{% hint style="success" %}
**Best practices**

* Start broad. Add one filter at a time.
* Prefer Save Views for repeatable lists.
* Name views by intent, such as `Team — Open items`.
* Use sorting to answer one question, such as: “What’s due next?”
* Keep shared views stable. Make variations as copies.
  {% endhint %}

#### Sort rows

Sorting changes row order.

It does not change the underlying data.

* Click a column header to sort ascending.
* Click again to sort descending.
* Use multi-column sorting, if enabled.

{% hint style="info" %}
Screenshot placeholder: column header showing sort indicator and the first few rows reordered.
{% endhint %}

#### Save the setup

Most configurations save filter and sort changes automatically.

When **Save as new view** appears, use it for variations.

Use [Save Views and Templates](/getting-started/save-views-and-templates.md) when shared standards are required.

Name the variation so it is obvious who it is for.

For example: `Me — Open items`, `Team — Weekly review`.

### Best Practices

* Add one filter at a time to validate results.
* Duplicate shared views before large changes.
* Keep shared view filters stable for reporting consistency.

### Summary

Filters and sorting define the dataset and review order for a view. Use a Save View to reuse the configuration.

Related:

* [Creating and Customizing List Views](/getting-started/creating-and-customizing-list-views.md)
* [Save Views and Templates](/getting-started/save-views-and-templates.md)


---

# 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://help.transform.ai/getting-started/filtering-and-sorting-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.