# 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](https://olddocs.exivity.io/3.4.3/data-pipelines/reports) 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](https://3540922554-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LHEKskLK6aXinV75Knl%2F-LbX7L7A01g-WFOcZpEW%2F-LbXN-PfSwanIfkdqlz-%2FmetadataShape.png?alt=media\&token=68093bc3-7387-45bc-8562-a7e11e1c22ab)

#### 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 ](https://3540922554-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LHEKskLK6aXinV75Knl%2F-Lhtxxm9bITzQXOC661o%2F-LfUYMisnVAe7qo-DTUh%2Fimage.png?generation=1561119429123296\&alt=media)

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](https://3540922554-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LHEKskLK6aXinV75Knl%2F-LbXNroFqrxxECCtfCOr%2F-LbXSUl36mruUUdgcXJ8%2FassociateMetadata.png?alt=media\&token=49e5376f-4a04-4a1d-9938-eda7abc0d7d7)

{% 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](https://3540922554-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LHEKskLK6aXinV75Knl%2F-LbXNroFqrxxECCtfCOr%2F-LbXTtICthOhelFnIkPV%2FstoringData.png?alt=media\&token=08e679bb-d434-449c-a5de-f12ec9e87fcf)