Autofill a List Field Based on Another Field's Value

Autofill a List field automatically selects its value based on what a user enters in a related field, so the value only has to be chosen once instead of twice. Rather than copying text between fields, Autofill matches the source value against the receiving field's own list and selects that matching option for the user. This removes repetitive selection across fields that share common values.

Autofill a List field is configured at the field set level. You identify one field as the source and one or more receiving fields. When a user enters a value in the source field during data entry, Claravine autofills that same value in each receiving field and matches and selects from the list automatically. Autofilled fields are read-only, so users cannot edit them directly.

This relationship is configured once at the field set level, but it applies everywhere those fields appear. Any template using the source and receiving fields will follow the same behavior.

Autofill helps your team:

Reduce manual data entry. Selecting a value in one field populates related fields automatically.
Eliminate "super-list" workarounds. Keep lists properly structured instead of flattening multiple lists into one oversized list to avoid repeat selections.
Improve data consistency. Values propagate from a single source of truth, cutting down on mismatches across related fields.

Available for field sets where the receiving field is a dropdown or dependent list.

How to Configure Autofill a List Field

It is best practice to review the source list and receiving list columns to ensure they match before implementing this.

Navigate to Elements > Field Sets and open the field set you want to configure.
Select the receiving field. It must be the first column (key) of a dependent list type.
In the side panel, locate Extract Data and select Autofill.
Use the Fill from field picker to select the source field. The source can be any single-value list type, including powered lists.
Save the field set.

Note: If the source field is later deleted, the receiving field displays an error state in the field set.

Example Workflow

The organization has 2 lists: Region, Country, Agency and Country, Language

The desired workflow is that the user selects a Region, Country, and Agency, and the Autofill a List Field functionality autopopulates the Country field to select the appropriate Language.

A Field Set includes all columns of both Lists. The administrator edits the Country (for Language list) field.

The Country (for Language) field is mapped to the correct List, in the Extract Data section, they choose Autofill. In the Fill From Field, they select the source field "Country".

For Users: Entering Data with Autofill

Once Autofill is configured, data entry is streamlined. See how the Country field autofills into the Country (for Language) field, and the Language and Language Abbreviation fields autofill.

Users select a value in the source field and watch the receiving field populate automatically.
Review autofilled values. They are locked and cannot be edited directly.
If a receiving field stays blank, check that the source field has a value and that the value exists in the receiving field's list.

Tips and Best Practices

Source and receiving fields must be in the same field set. Autofill only works between fields within a single field set. Cross-field-set relationships are not supported in this release.
Required fields still validate at submission. If a receiving field is marked Required, the source field must have a value. A blank source means a blank receiving field, which blocks submission.
No match means no fill. If the source field's value doesn't exist as an option in the receiving field's list, the receiving field stays blank and submission is blocked. Autofilled fields are read-only, so users cannot edit them directly.
Powered lists are supported as the source field type.
Receiving fields must target the key column. Autofill only populates the first (key) column of a dependent list. Derived columns are not supported as receiving fields.
Multiselect source fields are not supported. The source field must be a single-value list field. Multiselect fields are blocked at field set configuration.