> 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.md).

# Manage tables

Insert items related to your main context in the form of tables.

{% embed url="<https://www.youtube.com/watch?v=8pwGLXwe5Vw>" %}

We are going to go through **3 simple steps** to achieve this:

* Create several tables in a document
* Filter these tables to display only the relevant data
* Sort the tables by the criterion of your choice

{% hint style="info" %}
**Prerequisites**

* Have a template ready with the main object configured
* Choose a use case where the main object has related items (e.g. Opportunity, Quote, Account...)
  {% endhint %}

## Why use tables?

**What is a Gonexa "Child object"?**

A table corresponds to a **related list** in Salesforce. For example, if I am on an account, the contacts are children of that account. If I am on an opportunity, the opportunity products are children of the opportunity.

These relationships can be **standard** or built via **custom fields**. Gonexa technology simply lets you display the information related to your context.

## In this section

* [Create a table in a template](/doc/en/getting-started/manage-tables/create-table-in-template.md)
* [Filter table data](/doc/en/getting-started/manage-tables/filter-table-data.md)
* [Sort table data](/doc/en/getting-started/manage-tables/sort-table-data.md)
* [Group table data](/doc/en/getting-started/manage-tables/group-table-data.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://university.gonexa.fr/doc/en/getting-started/manage-tables.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.