> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/table-view.md).

# Table view

Create, filter, and edit records in rows and columns.

Use a Table view to work with records in rows and columns. This is the default view for a new table and provides a broad choice of features.

<figure><img src="https://3739718108-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwCp7NT87JGgngrkhfHT%2Fuploads%2FSdJ5KhGVvsvKifP08nI3%2Ftable_view.png?alt=media&amp;token=da7778cd-8e10-4309-8f5c-7497d15d6c97" alt=""><figcaption></figcaption></figure>

In **Table view** you can:

* Use **Hide columns** or **x hidden columns** to show or hide columns, **Create field** in the table, **Add logic column** to the view
* Use **Filter** to show only the records you need.
* Use **Group** to group your records in the view.
* Turn on **Inline Editing** to edit data directly in the table view, like in a spreadsheet.
* Open **More actions** to:
  * Use [**Bulk edit**](/user-hub/common-tasks/work-with-data.md#bulk-edit-records) to update all record in the view at once.
  * Use [**Import data**](/builder-hub/design-your-app/import-and-export-data/import-data.md) to import to this table.
  * Use [**Export data**](/builder-hub/design-your-app/import-and-export-data/export-data.md) to export the data that are displayed in this view.
  * [**Integrate API**](/getting-started/ninox-api-getting-started/intro-to-the-ninox-api.md) to connect your app with other systems and apps.

You can also change table columns directly by clicking the column title.\
In the menu, you can choose:

* **Rename column**
* **Duplicate column**
* **Insert column left** or **right**
* **Sort** in ascending or descending order
* **Group by this column**
* **Aggregation**, depending on the data type, which you can display in the footer with **Show footer**
* [**Conditional formatting**](/builder-hub/visualize-and-organize-your-data/customize-your-tables/style-your-tables-with-conditional-formatting.md)
* **Hide column**

{% hint style="info" %}
To change the column order, drag a column header to the required position.\
To change a column's width, drag the header's right edge.
{% endhint %}

Use **+ New column** in the last column header to:

* **Create field**\
  Create a new data field in the current table. The field is also added to the form view.
* **ƒx Add logic column**\
  Open the [**Logic** editor](/ninox-scripting/automate-your-workflows/explore-core-scripting-elements/logic-editor-features.md) and enter plain text or logic to gather and display data from your app.

  The script is saved only in this table view column.
* Select an existing field that is currently hidden in the table view.\
  Use **Search** above the displayed fields to find it.

{% hint style="warning" %}
Avoid large, performance-intensive scripts in the calculated column. The script runs in every row each time the view opens, which can slow down daily work.
{% endhint %}

{% hint style="warning" %}
The script of the calculated column is deleted if you delete the column or the whole view.
{% endhint %}


---

# 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://docs.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/table-view.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.