> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.md).

# Wildcard characters

### Introduction

You can use wildcard characters in the source file name, if required.

Wildcard characters can be used if you don't know the source file name, (e.g. the file name is a date and time stamp) or, if you want to import more than one source file.

Fields that accept wildcard characters expect a.NET regular expression, with the following exceptions:

* **?** is treated as **.** (matches any single character)
* **\*** is treated as **.\*** (matches any one or multiple characters)
* **.** is treated as **.** (an escaped full stop/period)

**Warning:** While **.** characters are automatically escaped, (i.e. ‘.’ is interpreted as ‘.’), parentheses and square brackets characters are not. So, if you use a parenthesis or bracket character in the field, you must escape it with a backslash in front unless you are using the parenthesis/bracket as part of.NET regular expression syntax. For example, to match the name ‘Doc (v1.0)’, you must enter ‘Doc (v1.0)’.

### Use case

For example, in a source file name field, wildcard characters can be used if you don't know the exact source file name, (e.g. the file name is a date and time stamp), or if you want to import more than one source file (e.g. multiple files with slightly different names).

### Definition

Wildcard characters are:

<table><thead><tr><th width="96">Character</th><th>Definition</th></tr></thead><tbody><tr><td>?</td><td>Represents any alphanumeric character in the position it occupies. This wildcard character can appear at the beginning of a filename, middle of a filename, or at the end of a filename.</td></tr><tr><td>*</td><td><p>Represents zero, one, or multiple alphanumeric characters in the position it occupies. This wildcard character can appear at the beginning of a filename, in the middle of a filename, or at the end of a filename.</p><p><strong>Note:</strong> If only '*' is used as the file name, all files within the source folder will be imported.</p></td></tr></tbody></table>

### Examples

Wildcard examples are:

<table><thead><tr><th width="126">Filename</th><th>Function</th></tr></thead><tbody><tr><td>achieve?.csv</td><td>Matches any twelve-character filename such as <em>achieved.csv</em> or <em>achiever.csv</em>. Does not match <em>achieve.csv</em> or <em>achievement.csv</em></td></tr><tr><td>e*t*.csv</td><td>Matches any filename such as <em>event.csv</em>, <em>elective.csv,</em> <em>electronics.csv</em> or <em>electronics1018.csv</em></td></tr><tr><td>Data \(*\).csv</td><td><p>Matches any filename starting with Data, followed by something in parentheses, followed by <em>.csv</em>, such as <em>Data (v1.0).csv</em> or <em>Data (ABC).csv</em></p><p><strong>Note:</strong> Parentheses characters must be escaped with a backslash in front, i.e. <strong>\(</strong> and <strong>\)</strong>.</p></td></tr><tr><td>eng*.csv</td><td>Matches any filename such as <em>english.csv</em>, <em>engineers.csv, engineering.csv</em>. or <em>eng1018.csv</em></td></tr><tr><td>*.*</td><td>Matches any filename with any file extension.</td></tr></tbody></table>


---

# 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.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.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.
