> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/schemas/repeatable-field-links/set-up-repeatable-field-links.md).

# Set up Repeatable Field Links

Link a source repeatable field to one or more dependent repeatable fields.

Configure a source repeatable field to drive one or more dependent repeatable fields, so that adding an entry in the source automatically creates a matching entry in every linked field. See [Repeatable Field Links](/technical-information/users/standard-registry-users-schemas-and-policies/schemas/repeatable-field-links.md) for how linked entries behave when the form is filled in.

## Prerequisites

* You are signed in as a Standard Registry user.
* The schema is open in the Schema Editor in **DRAFT** status.
* The schema contains at least one repeatable field (**Allow multiple answers** enabled) to use as the source, and at least one more to use as the dependent.

## Steps

### 1. Open the Repeatable links tab

Switch to the **Repeatable links** tab in the Schema Editor. The tab lists the links already defined for this schema, or shows `No repeatable field links in this schema.` if there are none.

### 2. Add a link

Fill in **Add repeatable field link** and select **Add link**:

* **Source array**, the repeatable field that drives the group, for example `Project Location`.
* **Dependent array**, the repeatable field that should follow the source, for example `Baseline Emissions`. It can live in a different schema of the same document.
* **Entry display name** (optional), a field from the source entry used to label each entry in the form.

Repeat to add more links. One source can drive several dependents, and a dependent can itself become the source for the next link. Build chains top down: add the parent link before using its child as a source.

### 3. Copy values between entries (optional)

Before selecting **Add link**, use **Add pair** to map a field from the source entry to a field in the dependent entry. Pick the **Source field** and the **Dependent field**, and the value is copied automatically and shown read-only in the dependent entry. Add as many pairs as you need. They appear under **Copied values** on the link card, and **Remove pair** deletes one.

### 4. Save the schema

Select **Save all**. Links, entry display names, and copied value pairs are stored with the schema.

## Result

The schema stores the configured links. When the schema is used in a policy:

* Adding a source entry creates a matching entry in every linked field, labeled with the entry display name.
* Copied fields arrive filled and read-only, and update when the source value changes.
* Removing a source entry opens a **Delete entry** confirmation, and confirming removes the matching entry from every linked field.

## Troubleshooting

**The dependent field still shows its own add and remove controls.**\
The link was not saved. Reopen the **Repeatable links** tab and check that the link appears on a card, then select **Save all**.

**I cannot add a condition on a field inside a linked entry.**\
This is by design. Fields inside a repeatable group are excluded from the condition pickers because the rule could not be enforced on the server. See [Repeatable Field Links](/technical-information/users/standard-registry-users-schemas-and-policies/schemas/repeatable-field-links.md#conditions-and-repeatable-groups).

## Related

* Concept: [Repeatable Field Links](/technical-information/users/standard-registry-users-schemas-and-policies/schemas/repeatable-field-links.md)
* Concept: [Schema Editor](/technical-information/users/standard-registry-users-schemas-and-policies/schemas/schema-editor.md)