# Creating List Lookup Maps

The List Lookup map uses a list of values for both the input field and the output field. For example, your source contains names of states in abbreviated format (e.g.

CA for California, NM for New Mexico, etc) in the input field, and you need to convert it into fully spelled-out states in the output field (e.g. California or Texas). You define such a list of values in the lookup grid in the properties of the List Lookup map object. The value is then looked up in the grid when your dataflow runs.

{% embed url="<https://youtu.be/TDm6yCqWU8g?feature=shared>" %}

To add a List Lookup mapping, drag the *List Lookup* object from the *Maps* group in the Flow toolbox and drop it on the dataflow.

An example of what a *List Lookup* object might look like is shown below:

![](/files/Xi9jy7U7Rh6PIyHYvkA8)

If a value is not found in the lookup list, the following actions are available:

* Assign value, add warning and proceed with these choices:
  * *Source value* – passes the input value through when there is no match
  * *Assign a null value* – outputs a null value when there is no match
  * *This value* – assigns the value provided here when there is no match
* *Add Error Message* – an error is triggered for the record that has no match in the lookup list.
* *Case Sensitive Lookup* – select this option when you need case-sensitive comparison of string values.
* *General Options screen:* This screen shares the options common to most objects on the dataflow.

## **Usage**

A fragment of a dataflow with a List Lookup object is shown below:

![](/files/1h1XCI6hPvNIdjtaWHYm)


---

# 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://documentation.astera.com/astera-data-stack-v6/dataflows/maps/creating-list-lookup-maps.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.