> 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.206/help-center-index/troubleshooting-index/errors-index/ibm-rational-doors-next-generation-error-solutions/oh-doors-next-0043.md).

# OH-DOORS Next-0043

## Description

When you encounter an error **OH-DOORS Next-0043**, then the following error message will appear:

**OH-DOORS Next-0043**: The module of an artifact cannot be changed. Hence, map the "Module" field only for create. We need to skip this field synchronization when the entity getting updated. To skip this field synchronization set the "Create" option under "Sync When?" settings in the field mapping.

## Cause

* This error will come when DOORS Next is the target end system and the "Module" field is mapped.
* Module of an artifact can't be changed in the end system once the artifact is created in the module.
* Thus whenever an update comes on an entity with "Module" field change, then an error will encounter.
* This behavior corresponds to the DOORS Next end-system behavior i.e.\
  **once a shared artifact is created i.e artifact created under the module then the module of an artifact cannot be changed**

## Solution

* The **"Module"** field must be mapped for **Create** event only.
* For doing this configuration, skip the **"Module"** field synchronization by setting **"Create"** option under **"Sync When?"** settings in the field mapping.
* For information on **"Sync When?"** setting, refer to document [Advance Settings Sync When?](/v7.206/integrate/configure-integrations/mapping-configuration.md#sync-when)


---

# 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.206/help-center-index/troubleshooting-index/errors-index/ibm-rational-doors-next-generation-error-solutions/oh-doors-next-0043.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.