> For the complete documentation index, see [llms.txt](https://docs.trymito.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trymito.io/how-to/bulk-column-header-edits.md).
# Bulk column header edits
Transform all of the column headers in your dataframe with just one click of a button.
## Why bulk column header edits
Sometimes you need to make the same edit to all of your column headers. If you have many columns, it take a lot of time to update each column header one at a time. For example, after constructing a pivot table, you might want to remove the aggregation type from the column header. Bulk column header edits let you update all of your column headers at once.
## How to bulk update column headers
1. Open the `Data` tab.
2. Click `Rename Columns`.
3. Use the taskpane to convert the column headers to uppercase/lowercase, or find and replace text the column headers.
---
# 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.trymito.io/how-to/bulk-column-header-edits.md?ask=&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.
