> 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/10.2-analytics/pentaho-interactive-reports-cp/customize-an-interactive-report/reorder-and-adjust-columns.md).

# Reorder and adjust columns

To change the order of columns in your report, choose the column you want to move, then drag it to the desired location. Alternatively, choose the column you want to move, click the down-arrow, and choose **Move** (**Left** or **Right**) from the menu.

![Move Interactive Reports columns](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-1f2304e485966dd5cc8eaeed04a001f7f01131af%2FCustomize_PIR_Move_Columns.png?alt=media)

To adjust a column's width, choose the column, then click the vertical line that divides the column headers. Move the line left or right to adjust the column width.

![Change Interactive Reports column widths](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-9f9b6a4f9bbb0a6c06293cc08d279679f110d731%2FCustomize_PIR_Change_Column_widths.png?alt=media)


---

# 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/10.2-analytics/pentaho-interactive-reports-cp/customize-an-interactive-report/reorder-and-adjust-columns.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.
