> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pentaho-dashboard-designer-cp/advanced-topics/use-data-tables-in-a-dashboard/updating-the-data-table-display.md).

# Updating the data table display

You can edit the data table display directly in the dashboard panel.

* **Sorting Column Data**

  To change the sort order data under a column, click the drop-down arrow in the header and choose **Sort Ascending** or **Sort Descending**. You can also hide one or more columns by disabling the appropriate check boxes next to the column names.
* **Adjusting Column Width**

  You can adjust the width of a column by clicking the right border of the column header and dragging it to the right or left. Release the mouse button when you are done.
* **Moving Columns**

  To move the placement of a column, click and drag the column to the appropriate location in the data table.
* **Paginating**

  The pagination feature allows you to page through a large number of records.


---

# 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.pentaho.com/pba/pentaho-dashboard-designer-cp/advanced-topics/use-data-tables-in-a-dashboard/updating-the-data-table-display.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.