# OH-Micro Focus ALM/QC-012656

## Description

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

Micro Focus ALM/QC-012656: Test set folder cannot have duplicate name. Server error: Duplicate Test Set Folder: `<Exception Message>`

**Example:**\
Micro Focus ALM/QC-012656: Test set folder cannot have duplicate name. Server error: Duplicate Test Set Folder: 'A'\
OpsHub-012654: Error occurred in HPQC CRUD Request execution for operation createHpqcEntity.\
OH-Micro Focus ALM/QC-0055: Error encountered while creating new entity of type: test-set-folders

## Cause

* User will encounter this error in the following scenario:
  * Entity with the same name that is already there within same parent.\
    **For example:**
    * The Root folder has three child Test Set folders named "Folder-1", "Folder-2", and "Folder-3". If you change "Folder-1" name to "Folder-2", then <code class="expression">space.vars.SITENAME</code> gives the above mentioned error.
    * The Root folder has two child Test Set folders named "Folder-1", "Folder-2". Now if Test Set Folder getting synchronized is having name "Folder-1" then such processing failure can occur.

## Solution

User can apply a solution which results into unique Test Set folder names under same parent. Below are few examples for the same:

1. Create/Update entity in the source such that entity does not have duplicate name.
2. Update mapping such that unique name appears for synchronization. Refer to the following example for advance mapping:

### Update mapping such that Test Set Folder name = {name} + {source entity Id}. Below is a sample advance XML for mapping:

```xml
<Name xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:value-of select="concat(SourceXML/updatedFields/Property/Name, ' [', SourceXML/opshubEntityId, ']')"/>
</Name>
```

If the source entity name is "QA folder" with internalId 22, it will create folder with name `QA folder [22]`.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://opstech.gitbook.io/opstech-docs/7.223/help-center-index/troubleshooting-index/errors-index/microfocus-error-solutions/oh-microfocus-012656.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.