# Metadata

After you have prepared a new report and thereby created accounts, you might want to have the ability to store related account information per account. Exivity allows you to do this at the **accounts overview page** but first we will have to create a **Metadata Defenition** before we can associate it to a [report](/2.10.2/data-pipelines/reports.md) and its levels. Apart from applying etadata to **Accounts**, as of version 2.10.1 it is also possible to apply metadata to **Services**.

## Step 1: Defining metadata fields

At the **metadata page** you define the type of form fields you want to use at the **accounts overview page**.

![Defining form fields](/files/-LbXN-PfSwanIfkdqlz-)

#### Field label

The field label represents the name of your form field

#### Type

The type field represents the eventual value type. At this moment Exivity offers you the following types:

1. String 
2. Number 
3. Date
4. List

### Validation

It is possible to configure field contents validation using a regular expression, by expanding the **options** on the right hand side. The below shows an example on how to define a GUID validation regex:

![Field data validation ](/files/-LfUYMisnVAe7qo-DTUh)

Always ensure to enclose your regex between two slashes (**/**), for example:

```
/^(\{{0,1}([0-9a-fA-F]){8}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){4}-([0-9a-fA-F]){12}\}{0,1})$/
```

## Step 2: Associate metadata to report levels

Now that we have defined the metadata, we would like to associate it to a report and its levels at the **reports page**. You can associate different metadata to each level within the same report.

![Associating metadata to report levels](/files/-LbXSUl36mruUUdgcXJ8)

{% hint style="info" %}
If you are updating or creating a report, do not forget to (re-)prepare your report.
{% endhint %}

## Step 3: Store related account information

We are now fully setup to store related information at the **accounts overview page**.

![Storing address information for an account](/files/-LbXTtICthOhelFnIkPV)


---

# 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/2.10.2/data-pipelines/metadata.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.