> For the complete documentation index, see [llms.txt](https://help.bioinsight.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.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/references/configure-multiple-identical-netpathprefixsearch-values.md).

# Configure Multiple Identical netPathPrefixSearch Values

It is possible to provide support for multiple, identical *seqservice.netPathPrefixSearch* property values. This is achieved by using the *seqservice.eventFileDirsToUseForSearchReplacePair* properties. These properties can be used to specify the mappings between search replace pairs and their associated event directories.

* The value of the *seqservice.eventFileDirsToUseForSearchReplacePair* property is a comma-separated list of event file directory suffixes to be applied to the search/replace pair.
* If the property is not supplied (or the value is left empty), the behavior is unchanged. In this case, the search/replace pair is treated as global and applied to all active event file directory suffixes.

{% hint style="info" %}
By default, BaseSpace Clarity LIMS does not specify the *eventFileDirsToUseForSearchReplacePair* property. If you want the search/replace pair to apply only to a subset of the event file directories, you must supply the property manually.
{% endhint %}

The following example uses a MiSeq installation to show several configuration options, with comments. Similar configuration may be applied for installations of other Illumina instrument integrations (eg, MiSeqDx, NextSeq).

Note that the last part of this example shows configuration that results in an error.

{% code overflow="wrap" %}

```markup
miseq.v8.seqservice.eventFileDirectory.1 '/mnt/MiSeq1/data/gls_events'
miseq.v8.seqservice.eventFileDirectory.2 '/mnt/MiSeq2/data/gls_events'
miseq.v8.seqservice.eventFileDirectorySuffixes '1,2'

miseq.v8.seqservice.netPathPrefixSearch.1 'Y:\'
miseq.v8.seqservice.netPathPrefixReplace.1 '/mnt/Miseq1/data/'
miseq.v8.seqservice.eventFileDirsToUseForSearchReplacePair.1 '1' // just use search/replace pair 1 in dir 1
 
miseq.v8.seqservice.netPathPrefixSearch.2 'Y:\'
miseq.v8.seqservice.netPathPrefixReplace.2 '/mnt/Miseq2/data/'
miseq.v8.seqservice.eventFileDirsToUseForSearchReplacePair.2 '2' // just use search/replace pair 2 in dir 2
 
miseq.v8.seqservice.netPathPrefixSearch.3 'A:\'
miseq.v8.seqservice.netPathPrefixReplace.3 '/mnt/Miseq2/data/'
miseq.v8.seqservice.eventFileDirsToUseForSearchReplacePair.3 '1,2' // use search/replace pair 3 in dir 1 AND 2
 
miseq.v8.seqservice.netPathPrefixSearch.4 'B:\'
miseq.v8.seqservice.netPathPrefixReplace.4 '/mnt/Miseq2/data/'
miseq.v8.seqservice.eventFileDirsToUseForSearchReplacePair.4 '' // global, use this search/replace pair in all dirs
 
miseq.v8.seqservice.netPathPrefixSearch.5 'C:\'
miseq.v8.seqservice.netPathPrefixReplace.5 '/mnt/Miseq2/data/' // no replace pair dir prop specified = global, use this search/replace pair in all dirs
 
miseq.v8.seqservice.netPathPrefixSearch.6 'Y:\'
miseq.v8.seqservice.netPathPrefixReplace.6 '/mnt/Miseq2/data/'
miseq.v8.seqservice.eventFileDirsToUseForSearchReplacePair.6 '1' // duplicate search value (Y:) for event file dir 1 - ERROR
 
miseq.v8.seqservice.netPathPrefixSearchReplaceSuffixes '1,2,3,4,5,6'
```

{% endcode %}


---

# 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://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/references/configure-multiple-identical-netpathprefixsearch-values.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.