> 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/cleanse/change-case.md).
# Change Case
In this document, you’ll learn how to use the Change Case function in Astera Dataprep to convert text data to lower, upper, or title case.
1. To begin, click on the *Cleanse* option in the toolbar and select *Change* *Case* from the drop-down.
2. This will open the *Recipe Configuration – Change Case* panel.
3. In this panel, you’ll configure the following options:
* Column Selection Properties
* **Apply to entire dataset**: Applies the case change to all columns in the dataset.
* **Apply to specific column(s)** – Applies the change only to selected columns.
* Case Type
* **Lower**: Converts all text to lowercase.
* **Upper:** Converts all text to uppercase.
* **Title**: Capitalizes the first letter of each word.
4. Once you’re done, click *Apply* *.* In the Grid, you’ll see that the data in the *StoreName* column has been converted to uppercase.
5. Alternatively, you can right-click on a column header in the Grid and select *Cleanse > Change Case.* The same configuration panel will appear with the column already selected. Make any changes you need and click *Apply* to update your data.
---
# 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/cleanse/change-case.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.