# Metadata dependencies Metadata dependencies are **logic rules** that control how metadata behaves based on other metadata values: they let you show or hide fields, set default values, and restrict options so that your data stays relevant, accurate, and consistent. ### Create a dependency Dependencies are created at the metadata field level by defining a combination of: * **asset type**: filtered list of assets (*all assets, images,...)* * **trigger**: a condition that when honoured triggers action (s) * **action(s)**: an automated action(s) applied to another metadata field or field group

\ The dependency tab is accessible by editing a metadata supporting dependencies {% hint style="info" %} Only metadata of type Boolean, List (single value) and list (multiple values) supports dependencies {% endhint %} **Supported conditions (trigger)** The following conditions can be used to trigger a dependency (this depends on the type of metadata used to create the dependency) | Condition | Boolean | List (single-value) | List (multiple-value) | | -------------- | -------------------- | -------------------- | --------------------- | | `is_true` | :white\_check\_mark: | :x: | :x: | | `is_false` | :white\_check\_mark: | :x: | :x: | | `is_empty` | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | | `is_not_empty` | :white\_check\_mark: | :white\_check\_mark: | :white\_check\_mark: | | `is_in` | :x: | :white\_check\_mark: | :white\_check\_mark: | | `is_not_in` | :x: | :white\_check\_mark: | :white\_check\_mark: | | `is` | :x: | :x: | :white\_check\_mark: | | `is_not` | :x: | :x: | :white\_check\_mark: | **Supported actions**

Action	Metadata group	All metadata type	Boolean	List (single-value)	List (multiple-value)
`is_hidden` Hides the metadata / group of metadata	✅ (Hides all the metadata in the group)	✅	✅	✅	✅
`is_required` Metadata needs to be filled in to save	❌	✅	✅	✅	✅
`allow_values` Set the values that will be shown to the user (subset of the metadata options list)	❌	❌	❌	✅ (multiple values)	✅ (multiple values)
`set_values` Set the value(s) of the metadata	❌	❌	✅	✅	✅

{% hint style="info" %} Certain combinations of dependencies, triggers, and actions are not allowed because they would create conflicts on the metadata level {% endhint %} When a dependency is enabled, it applies to assets. In the asset details modal / info sidebar, metadata fields controlled by a dependency are marked with a link icon (hover over the icon to see the dependency details):

Some conflicts may arise when a dependency is enabled (for example if the dependency is setting a value to a metadata that has already a different one). \ \ Conflicts (if any) are indicated in a banner located on top of the panel. Click on Solve conflicts to highlights and fix the issues. \
--- # 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://docs.scaleflex.com/digital-asset-management-dam/settings/metadata/metadata-dependencies.md?ask= ``` 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.