> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/delete-data-object.md).

# Delete Data Object

## Description

The *delete data object* part allows you to remove a variable name and corresponding values from the context, effectively resetting the data model at that point in runtime. You can apply it to a single data object (text, numeric, date), a container of multiple objects (container.object1, container.object2), or a collection.

## Use

This part is used extensively in most logic models. It allows you to do the following:

* Clear out a user input field; for example, when a user clicks "new" the system deletes any previously input information.
* Reset an entire form. This applies if you put every field in the form in the same container; for example, *new\_client\_details.company\_name, new\_client\_details.company\_address.*
* Clear out any prior results from a "get records" statement prior to retrieving fresh records.
* Reset a collection when the system adds items to a collection as the user answers questions.
* Reset a variable used for application navigation; for example, after a user clicks a button, the system resets the button and logic flow by deleting the button data object.

## Tips & Tricks

When building an application, you may create a number of "temporary" variables used in processing steps, such as calculating intermediate numbers or setting flags associated with particular logic paths. Placing these in a container called "tmp" allows you to quickly clear them at the end of processing by deleting "tmp" with this part. This is also good practice for processing.

When dealing with a form consisting of user inputs, use a container as a scoping name ("client details", for example), so you can easily clear the form values in one step by deleting the data object called "client details" at the appropriate time.

## Editor Fields

| Field Name                                               | Description                                                                                                                                                                                                 | Type/Options | Optional/Mandatory |
| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Data object                                              | This is the data object, container, or collection name that you want to clear from the runtime context.                                                                                                     | Text         | Mandatory          |
| <p>Save data-object in log<br>(Versions Prior to v8)</p> | <p>Setting this option to <em>Yes</em> logs the deletion in the changelog\_ctx. It defaults to <em>No</em>.<br>Change to <em>Yes</em> when using the LogicNets Assessment Framework.</p>                    | No \| Yes    | Mandatory          |
| Update change log (Version 8+)                           | <p>Setting this option to <em>Yes</em> tells the system to log the deletion in the changelog\_ctx. It defaults to <em>No</em>.<br>Change to <em>Yes</em> when using the LogicNets Assessment Framework.</p> | No \| Yes    | Mandatory          |
| <p>Update data log<br>(Version 8+)</p>                   | <p>This tells the system to update the data log when data object is cleared. It defaults to <em>No</em>.<br>Change to <em>Yes</em> when using the LogicNets Assessment Framework.</p>                       | No \| Yes    | Optional           |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/delete-data-object.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.