> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/textbox/clear-text-from-cell.md).

# Clear Text From Cell

This is a pre-built Action located under the captured textbox element. The functionality of this Action in Avo Assure is to clear the text from the textbox. The result of this operation is stored in a dynamic variable for further use during test execution.

## Syntax

**Input Value**: `N/A`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>N/A</td><td>Not Applicable</td><td></td></tr></tbody></table>

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable>(Optional);&#x3C;Dynamic Variable>(Optional)</td><td>Both dynamic variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Clearing Text from a Targeted text box**

In this example, we explain how to clear existing text from a specified text box during execution using the **Clear Text From Cell** action.

* **Action**: Clear Text From Cell
* **Input Value**: N/A
  * The **Clear Text From Cell** action does not required any input value in the **Input Value** column. It simply removes any existing text or content from the targeted text box.
* **Output Value:** {Status}
  * The result of the text clearing operation is stored in this **{Status}** dynamic variable with the following possible values:
    * **True**: If the text is cleared successfully.
    * **False**: If the text is not cleared successfully.
* **Logical Explanation**: The **Clear Text From Cell** action interacts with the specified text box and removes any existing content during test execution. After the operation is performed, the result is stored in the **{Status}** variable as true.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Far5Wrz7Nkf7oI3DAjkFv%2Fimage.png?alt=media&amp;token=08e224f6-f8d5-4d5e-8679-44c1fa1bebf1" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/web/textbox/clear-text-from-cell.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.