> 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/microfocus-error-solutions/oh-microfocus-012652.md).

# OH-Micro Focus ALM/QC-012652

## Description

When user encounters OH-Micro Focus ALM/QC-012652, then following error message will appear:

'OH-Micro Focus ALM/QC-012652 : Invalid Field name used in the mapping therefore error in response from Quality Center, because of: `<Exception from QC>` : Exception Message - `<Exception Message>`.

**Example:**\
OH-Micro Focus ALM/QC-012652 : Invalid Field name used in the mapping therefore error in response from Quality Center, because of: qccore.unknown-field-name : Exception Message - Entity: requirement doesn't have a field named: 'user-xx'

## Cause

* User might encounter this error in the following scenarios:
  * When a custom field that is used in mapping is available on Micro Focus ALM/QC UI as well as in <code class="expression">space.vars.OIM</code> mapping configuration, but it is not associated with the Requirement Type entity that is used in integration.\
    \&#xNAN;***For example***, the custom field `user-xx` is available on Micro Focus ALM/QC UI as well as in <code class="expression">space.vars.OIM</code> mapping configuration, but it is not associated with Requirement type entity that is used in the integration. Also, the user has used the custom field `user-xx` in the mapping between Requirement of Micro Focus ALM/QC and any other system.
  * When in an integration configured with criteria, the internal name for the field mentioned in the criteria query is incorrect.

## Solution

* To associate any custom field with the requirement type that is being used in integration, please refer\
  [How to associate a custom field with the Requirement](/v7.237/connectors/micro-focus-alm-qc.md#how-to-associate-a-custom-field-with-requirement)
* To determine the internal name for the criteria configuration please refer\
  [How to find the internal name](/v7.237/connectors/micro-focus-alm-qc.md#how-to-find-out-internal-name2fkey-in-versions)


---

# 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/microfocus-error-solutions/oh-microfocus-012652.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.