> For the complete documentation index, see [llms.txt](https://help.claritylims.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.claritylims.illumina.com/instruments-and-integrations/references/configure-support-samples-duplicate-names-different-indexes.md).

# Configure Support for Samples Having Duplicate Names with Different Indexes

To support planned run creation for samples having duplicate names with different indexes, updates are required on the library preparation workflow that these samples go through.

Follow these steps to update the output Naming Convention of the library preparation workflow.

1. Select the Configuration tab, and then select the Lab Work tab.
2. Under Master Steps, select the master step of the library preparation workflow (e.g., Library Prep Validation).
3. Navigate to the Step Type pane and update Naming Convention to

   <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">{SubmittedSampleName}_{OutputItemLIMSID}
   </code></pre>

<figure><img src="/files/Iflb8LuyKXPW0WCaYIrG" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://help.claritylims.illumina.com/instruments-and-integrations/references/configure-support-samples-duplicate-names-different-indexes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.