# Lookups

In certain scenario's it might be required to maintain a statis **Lookup** file in Exivity. For example, when no logical mapping can be done from certain cloud resources such as mapping of VMware datastores, Azure Resource Groups, T-Shirt Size / Flavor VM's, etc. To apply business logic such as Disk Tiering or Customer identifications, a static **Lookup** file can be a useful tool to close this gap in your data feed. In this chapter, we explain how to create, import and use a **Lookup** file in Exivity.

## Creating Lookups

To create a new **Lookup** file, browse to the **Data Pipelines** > **Metadata** menu and then click the **Create** **Lookup**. To create a new empty **Lookup**, provide a *name* and specificy the amount of *columns* and *rows* that you'll need (don't worry - you can add/remove columns and rows later): 

![Creating a new Lookup](/files/-LqkRwFpheiESwafgVF5)

After clicking the **Create** button an Excel-like grid will be shown. The first *row* of the lookup is considered the header which is mandatory. All rows afterwards are values that can be filled in according to your use case. In this example, we're creating a static mapping for *VMware Datastores*, where each *Datastore* relates to a specific *Department*:

![Adding values to a lookup file](/files/-LqkSYmMpeRGnlgeTOQG)

In case you want to remove or add a column/row: by right-clicking anywhere in the grid a pop-up will be shown from where you can chose to add/remove a column/row:

![Adding and removing columns and rows](/files/-LqkTM3nruVGT__hpt5J)

When you are finished, click the **Update** button.

{% hint style="warning" %}
NOTE: make sure there are **no empty rows** at the end of your lookup file. Failing to do so may cause an import error when using the **Lookup** in a **Transformer**
{% endhint %}

## Importing Lookups

In case you already have a Lookup file which you have created elsewhere (i.e. Excel sheet, or CSV export from a CMDB), Exivity offers you the ability to create a **Lookup** by importing that file.  

To import a CSV or Excel sheet as a **Lookup** file, browse to the **Data Pipelines** > **Metadata** menu and then click the **Create** **Lookup**. Now click the **Import** button in the area of the screen which is labelled as *Use existing.* Now it is possible to make some final changes to your file. Once finished, press the **Update** button to save your changes.

{% hint style="warning" %}
NOTE: make sure there are **no empty rows** at the end of your lookup file. Failing to do so may cause an import error when using the **Lookup** in a **Transformer**
{% endhint %}

## Using Lookup file in a Transformer

Once a **Lookup** is created, it is possible to import it in a [Transformer ](/3.5.4/data-pipelines/transform.md#overview)as a [DSET ](/3.5.4/advanced/digging-deeper/dataset-lifecycle.md#dsets)for correlating datasets and other use cases. Before opening your **Transformer**, the first thing to do is obtaining the correct **Lookup** file path for importing. 

To obtain this path, first open the **Lookup** using the *Lookups* menu. Then click the *Copy* icon to the right of the *FILENAME*:

![Copy Lookup path](/files/-LqkkHBDmeUtG86cROTC)

Once this has been done, now open your **Transformer**, and past the path of your **Lookup** as part of an [import ](/3.5.4/data-pipelines/transform/language/import.md#import-from-csv-files)statement:

![Importing a statis Lookup in a Transformer](/files/-Lqkl8WjswIVlBD_4Tjl)


---

# 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://olddocs.exivity.io/3.5.4/data-pipelines/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.