> 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/troubleshooting-index/errors-index/jama-error-solutions/oh-jama-0103.md).

# OH-Jama-0103

#### Description

When you encounter error OH-Jama-0103, then following error message will appear:

> OH-Jama-0103: Error occurred while updating entity in Jama. Child Item Type field can't be updated.

#### Cause

Probable cause for this issue is:

* For creating a Set in Jama, **Child Item Type** field must be present.
* Once a Set gets created in Jama with a specific Child Item Type, the child item type can't be modified through the Jama API.
* With respect to the above end system behavior, when any update comes on **Set** entity field **Child Item Type**, <code class="expression">space.vars.OIM</code> will raise this error.

#### Solution

Set **"Sync When?"** settings for the **"Child Item Type"** field to **"Create"**:

* Set the **"Child Item Type"** field to be mapped for the **Create** event only.
* To do this, skip update synchronization on the **"Child Item Type"** field by selecting the **"Create"** option under the **"Sync When?"** setting in the field mapping.
* For more information on the **"Sync When?"** setting, refer to the document [**Advance Settings Sync When?**](/v7.237/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.237/help-center-index/troubleshooting-index/errors-index/jama-error-solutions/oh-jama-0103.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.