# relations

{% hint style="info" %}
#### Experimental Feature

This configuration entry is related to an Experimental (Optional) feature called Cross-File Relations. Before you start to configure this section, make sure to read the page specific for this feature (accessible [here](../../optional-features/schema-improvements/cross-file-relations)) and [this](../../concepts/experimental-features) page that explains how to enable Experimental Features.
{% endhint %}

### Type: [Map](../types-and-objects/map)<[FileModelColumn](../types-and-objects/file-model-column), [FileModel](../types-and-objects/file-model)>

<details>

<summary>Versioning History</summary>

**API Version v1.0.0** - Introduced `relations` configuration option.

</details>

This object's entries are a key-value pair. When the schema is being generated, the remapper will identify the relations by using this configuration section to ensure that the you don't get reverse mapping errors in Prisma. This is a feature that is a bit harder to configure correctly, and as such we recommend that you familiarize yourself with the topics covered on [this](../../optional-features/schema-improvements/cross-file-relations) page. To tell Prisma Util how to handle your relations properly, add the following line to your exported configuration object:

{% code title="prisma-util.config.mjs" %}
```javascript
export default {
    // Other configuration lines
    relations: {
        "filePath1:Model1.column1": "filePath2:Model2"
    }
}
```
{% endcode %}

In this example, `column1` will have it's type changed to `Model2`.
