> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/connecting-lists-and-forms-to-a-database/applying-filters-to-lists.md).

# Sorting and Filtering Lists

To change the way data is displayed in a list.

If you want to make it so that your app only displays a particular subset of your data, you can create a data filter.

For example, let's take the app we've previously been working on, which allows you to browse vacation spots. Suppose you input all of your data into a Trips Collection with many Properties, one of which is a True/False criteria describing whether or not the trip is public. Let's say for your app, you only want to display trips that are public. You also want to sort the trips from low cost to high cost.

![Steps 4 and 5](https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-LihribgCtvrVPIWVpG8%2F-Lihtriuk_VEm6KcKRLZ%2FScreen%201%20Sorting%20and%20Filtering%20\(1\).gif?alt=media\&token=3377583b-ab9a-4e52-bf8c-40781670c046)

1. Insert a list
2. Select the database collection you want listed
3. Click 'Add another filter' to insert a custom filter
4. Select which Property you want the filter to depend on (in this case, Public)
5. Choose the condition of the Property that you want to filter for (True/False, Between, Includes, Excludes, etc)
6. Under Sorting select how you want to sort your list (in this example, Cost- Low to High)

 After filtering, only the trips that had been tagged as public showed up in the preview.


---

# 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.adalo.com/component-basics/connecting-lists-and-forms-to-a-database/applying-filters-to-lists.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.