> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/dataprep/layout/change-column.md).
# Change Column
In this document, you explore how to make changes to a column in Astera Dataprep.
1. To change a column, select the *Layout* option in the toolbar and select *Change Column* from the drop-down.
Alternatively, you can also right-click on the column you need to change and select the *Change Column* option from the drop-down.
2. Once selected, the *Recipe Configuration – Change Column* panel will open. Here, you can define the *Name, Operation,* and any related information depending on the *Operation* that you have selected.
* **Name:** The name of the column that needs to be modified.
* **Operation:** The modification that needs to be applied to the column. This drop-down consists of three options: DataType, Header, and Value.
* **DataType:** Select this if the column’s data type needs to be modified. If selected, you can use the Type drop-down to choose a new data type for the selected column.
* **Header:** Select this if a column’s header needs to be changed. If selected, you can specify a new header in the *Header* textbox.
* **Value:** Select this if you need to modify the value within a column. If selected, you can use the expression box to enter an expression that you want to be applied.
3. Once you are done with the necessary configurations, you can select the *Apply*  option for the changes to be applied to the selected column.
---
# 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://documentation.astera.com/dataprep/layout/change-column.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.
