> 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/remove-data-item.md).

# Remove Data Item

## Description

The *Remove Data Item* part allows you to remove a particular value or data object from within a collection. It is located in a process node under the *collections* dropdown menu.

## Use

You can use the *Remove Data Item* function to delete the value in a specific position within a collection.

## Tips & Tricks

This part only accepts the **position** of an item in a collection as the parameter for removal.

If, for example, you have a checklist of three items, and only the third item is checked in runtime, this occupies position 1 of the collection data model, unless and until item one or two in the UI is checked. At that point item 3 will move from position 1 to position 2 in the collection. As a consequence, you should always take care to remove the correct item.

You can use a loop to check the values in turn and take action when the item value matches, or you can use the query-collection part to identify the path of the item (see below) and then use the pattern matching part to extract the position.

```
/my_collection[_.this = 'value to be removed'] will give a result path of my_collection[n] where n is the position of 'value to be removed'
```

## Editor Fields

| Field Name | Description                                                                                                                                                                                                                                                                                            | Type/Options | Optional/Mandatory |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------ |
| Collection | This is the collection from which the system will delete the data object. Specify a pre-existing collection from which data will be deleted. Instead of typing the collection name, you can click the ellipses button to the right of the field and select a collection from the displayed data model. | Text         | Mandatory          |
| Position   | This is the position in the collection from which the system will delete data. Specify the numeric position within the collection. You can leave the field blank if you specified the position in the previous parameter using the *$(collection\_name)\[position#]* compound naming convention.       | Number       | Optional           |

## Example

Download the example project called [Add Change Remove Data Item](/release-9/example-gallery/example-projects-for-parts/add-change-or-remove-item-from-collection.md) to see this part in use.


---

# 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/remove-data-item.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.