Duplicate value on a unique field

The save was refused because another entry in the same collection already holds that value in a field marked unique. Find that entry, then either update it instead of creating a new one, change your value, or archive the old entry if it is no longer needed; archived entries do not count.

Requirements

A role that can edit entries in the collection. To turn uniqueness off, a role that can edit the collection's fields.

Why it happens

A field marked unique allows each value only once across the collection's entries. A recruitment firm marks the candidate email unique so the same person cannot be added twice. When a second entry tries to save an email that is already there, the save is refused and the field is named. See Fields: built-in and your own for what unique means.

How to fix it

1. Find the entry that holds the value. Search or filter the collection by that field. See Filter a view.
2. Decide which case you are in.
   • It is the same thing: the candidate is already there. Update that entry instead of creating a new one.
   • Your value is wrong: correct it and save again.
   • The old entry is obsolete: archive it. Archived entries are not counted, so the value becomes free.
3. If the field should not be unique at all, turn unique off in the field's settings. See Add or change a field.

Notes and limitations

• Uniqueness is checked within one collection. The same value in another collection is not a conflict.
• The check applies however the entry arrives: the form, an agent, an import, an automation, or your website. A website form that re-submits the same email is refused the same way.
• A slug never causes this error. When a slug is already taken, a numbered suffix is added automatically.
• A secret field cannot be unique, so it never causes this error.

Related

For other reasons an entry refuses to save, see My entry will not save.