What this does
The Reject duplicate values setting checks whether the value a respondent enters already exists in the same Airtable field across all records in the table. If a match is found, the form shows an error and prevents submission. This runs as a real-time check. The respondent sees the error as soon as they move away from the field, before they even try to submit.When to use it
- Unique email registration: prevent the same email from being submitted twice
- Unique order or ticket IDs: ensure each record has a distinct identifier
- Unique usernames or slugs: enforce uniqueness on a text field
- Unique barcode entries: prevent the same barcode from being scanned into two records
How to enable it
How the check works
When the respondent finishes typing and moves away from the field, Filla queries the Airtable table for any existing record where that field has the same value. If a match is found, the form shows an error and the respondent cannot submit. The check is case-sensitive for text fields.John@example.com and john@example.com are treated as different values.
The duplicate check queries your live Airtable table, so it reflects the current state of your data in real time. If a matching record is deleted between when the respondent filled the form and when they submitted, the check would pass.
Editor indicator
When Reject duplicate values is on, the field shows a teal No duplicates tag in the top-right corner of its card in the editor canvas.Common questions
Does it check against all records or just a view?
Does it check against all records or just a view?
It checks all records in the table, regardless of any view or filter you’ve set on the form. The check cannot be scoped to a view.
What error message does the respondent see?
What error message does the respondent see?
A default error message appears. Currently there is no option to customize the duplicate rejection error message (unlike custom validation rules, which have a customizable error message field).
Does this work in edit mode?
Does this work in edit mode?
In edit mode (when updating an existing record), the duplicate check ignores the current record’s own value. This prevents the respondent from seeing a false duplicate error when they haven’t changed the field.
Can I use this on a linked record field?
Can I use this on a linked record field?
Reject duplicates is available on text, email, URL, phone, and barcode fields. It is not applicable to linked record fields, which have their own count limits.