> 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/mapping-cardholder-data/mapping-a-value-that-doesnt-match-a-transformation.md).

# Mapping a value that doesn't match a transformation

### Introduction

When setting a transformation mapping, you will need to define what will happen if a source value doesn't match a transformation.

**Note:** If you have used a wildcard character to catch all values within a source field, selecting one of the below options has no effect.

If the source value doesn't match a transformation, you can choose to either:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ef9e048978bb04a5808a9f98095e1c6a1fc37cb9%2Ftransformationdoesn'tmatch.png?alt=media)

* **Don't change field**

  When adding a cardholder, the Gallagher Command Centre default will be used, if a default has not been specified the field will be set to blank.

When updating a cardholder, the existing value remains unchanged.

When importing a source value that doesn’t match a transformation for a booking field, the default value will be used.

* **Set to source value**

  This option effectively does a direct mapping. It matches the name of the data coming from the data source file to an Command Centre item name in Command Centre, and adds it with the default values on the Command Centre item.
* **Fail data record**

  The record will fail to import.

Use this to indicate that all possible values have been specified. If the source field contains a value that is not listed as a transformation, then the record is in error.


---

# 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/mapping-cardholder-data/mapping-a-value-that-doesnt-match-a-transformation.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.
