# Cross-reference lookups

## Introduction

**Cross-reference lookups** are used for cases where sets of static values are commonly known by another value. For example:

**Weight measurements**

| Term     | Also known as... |
| -------- | ---------------- |
| Kilogram | Kg               |
| Gram     | g                |
| Cup      | c                |

**Months of the year**

| Term     | Also known as... |
| -------- | ---------------- |
| January  | Jan              |
| February | Feb              |
| March    | Mar              |

If you have source data which includes values that always need to be changed to an alternative term, a cross-reference lookup can be used to transform required data fields.&#x20;

For example, you might have an incoming payload which has a 'renewal month' field with values in the form 'January', 'February', 'March', etc. but also have a target connection which only accepts months in abbreviated form - 'Jan', 'Feb', 'Mar', etc.

In this scenario, you could add 12 `replace` [transformation functions](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape/working-with-field-transformations/available-transform-functions.md) for any field that needs this conversion - but a more efficient approach is to add one `map` transformation function (associated with the appropriate **cross-reference lookup**) to required fields.

Patchworks provides a range of **cross-reference lookups** which you can [install](/product-documentation/process-flows/cross-reference-lookups/installing-cross-reference-lookups.md) and [use](/product-documentation/process-flows/cross-reference-lookups/using-a-cross-reference-lookup-in-field-transformations.md), or you can add your own.

## In this section

* [Accessing cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups/accessing-cross-reference-lookups.md)
* [Installing cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups/installing-cross-reference-lookups.md)
* [Adding a cross-reference lookup](/product-documentation/process-flows/cross-reference-lookups/adding-a-cross-reference-lookup.md)
* [Importing & exporting cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups/importing-and-exporting-cross-reference-lookups.md)
* [Using a cross-reference lookup in field transformations](/product-documentation/process-flows/cross-reference-lookups/using-a-cross-reference-lookup-in-field-transformations.md)

{% hint style="info" %}
If required, cross-reference lookups can also be updated via the Patchworks API. For more information please see our [Cross-reference lookup API ](/product-documentation/developer-hub/patchworks-core-api/core-api-spotlights/working-with-cross-reference-lookup-api-requests.md)section.
{% endhint %}


---

# 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://doc.wearepatchworks.com/product-documentation/process-flows/cross-reference-lookups.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.
