> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/getting-started/manage-tables/filter-table-data.md).

# Filter table data

Filters ensure that you only see the data that is relevant to your context.

{% hint style="success" %}
**Example**

Here, we want to show only the "Product" category in the 1st table, "Services" in the 2nd and "Options" in the last one. We use the same Salesforce object 3 times, but with different views.
{% endhint %}

## Identify the filter to use

A good knowledge of your Salesforce org is essential to identify the right filter to use, i.e. the field populated with the right data.

* If the field that will filter the data has not been created yet, make sure you create it and populate it

## Add the condition on the child object

* In the Gonexa Assistant component, edit the child object by clicking the pencil icon
* In the "Filter" section, add a record retrieval filter
* Find the field to use for the filter

{% hint style="success" %}
**Example**

Product Family = "Options"
{% endhint %}

![Adding a filter on the child object](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/0g3SC1hXubvy97H777RR/18-filtrer-donnee.gif)

## Check the filter

* Go back to your context (Quote, Opportunity, ...)
* Make sure the filtered field contains data
* Generate to check that the filter has been applied


---

# 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://university.gonexa.fr/doc/en/getting-started/manage-tables/filter-table-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.