> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/faqs/general-faqs/does-entity-delete-operation-supported.md).

# Does entity delete operation supported ?

## Description

Integration is configured from system A to system B. If entity is created/updated in system A then it will appropriately create/update in system B through <code class="expression">space.vars.OIM</code>.

Now if entity is being deleted in system A, will <code class="expression">space.vars.OIM</code> synchronize delete operation in system B as well so that entity in system B is deleted after synchronization?

## Solution

<code class="expression">space.vars.OIM</code> does not support delete operation. To work on the delete use case scenario, <code class="expression">space.vars.OIM</code> recommends adapting an approach of logical delete.

Follow the steps below to adapt logical delete approach:

1. Don't actually delete the entity but just mark the entity as deleted in some custom field or status that represents that an item has been deleted.
2. Do field mapping to map that custom field or status value that is representing deleted to appropriate destination field or value which is representing deleted in destination.
3. Once source side entity is marked deleted then <code class="expression">space.vars.OIM</code> will synchronize this value to target side to indicate that an item had been marked as deleted.


---

# 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.opshub.com/v7.237/help-center-index/faqs/general-faqs/does-entity-delete-operation-supported.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.