> 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/replace-null-values.md).
# Replace Null Values
In this document, you’ll learn how to use the Replace Null Values function in Astera Dataprep to handle missing data by replacing null strings or numerics with default values.
1. To begin, click on the *Cleanse* option in the toolbar and select *Replace Null Values* from the drop-down.
2. This will open the *Recipe Configuration – Replace Null Values* panel.
3. In this panel, you’ll configure the following options:
* Column Section Properties:
* **Apply to entire dataset:** The changes will be applied to the entire dataset.
* **Apply to specific column(s):** Allows you to apply changes to selected columns only.
* Replace Nulls:
* **Null strings with blanks:** Replaces all null strings with blank entries.
* **Null numerics with zeros:** Replaces all null numeric values with 0.
4. Once you’re done, click 
*Apply.* In the Grid, you’ll see that all specified null values have been replaced accordingly.
5. Alternatively, you can right-click on a column in the Grid and go to *Cleanse > Replace Null Values.* 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/replace-null-values.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.