> 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-0101.md).

# OH-DOORS Next-0101

## Description

When the user encounters an error **OH-DOORS Next-0101**, then the following error message will appear:

**OH-DOORS Next-0101**: TARGET\_LOOKUP Invalid: Missing field "`<Field Name>`" in Project "`<Project Name>`", Component "`<Component Name>`", Stream "`<Stream Name>`". Please check if there exists a case-sensitive field with name "`<Field Name>`" in Project "`<Project Name>`", Component "`<Component Name>`", Stream "`<Stream Name>`"

## Cause

When **Module Filter Query** setting is configured in integration for DOORS Next as source endpoint, and an error occurs for the field used in **Module Filter Query**, the cause is:\
**The field(s) used in Module Filter Query input does not exist as the field(s) in the end system for the artifact type for which integration is configured.**

## Solution

* Refer to the note(s) of the section [Synchronize artifacts from specific module(s)](/v7.206/connectors/ibm-rational-doors-next-generation.md#synchronize-artifacts-from-specific-modules)


---

# 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-0101.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.