FIELD FEATURES

Prevent duplicate field answers with Pro

Enable No duplicates on supporting Logical Forms fields, understand accepted-entry scope and matching, and customize the duplicate message.

2 min read · Updated November 19, 2026

Logical Forms Pro can prevent a supporting field value from being reused in another accepted entry for the same form. For example, use it on an Email field when one accepted response per normalized address fits your workflow.

Enable the rule

  1. Activate Pro alongside Core.
  2. Select a supporting field in the builder.
  3. Enable No duplicates in General.
  4. Optionally set Duplicate value message in Advanced.
  5. Save the form and test with controlled entries.

Supported types include Text, Paragraph, Email, Phone, Website / URL, Number, Date, Time, Hidden, Dropdown and Radio. Compound fields, multiple selections, Consent, Slider and Rating do not automatically provide this rule. Free shows a locked option on supporting types; while Pro is inactive, repeated values can be accepted.

Understand the scope

The rule applies to one form, one field and one value across accepted entries in the same live/test partition. It does not combine several questions into a unique key, enforce a site-wide user identity, or provide appointment inventory.

Blank normalized strings are ignored. Enable Required separately to require an answer. Zero is a real value. Enabling the rule does not repair or delete historical duplicates; future new or changed values are checked against existing accepted entries.

How matching works

Setting What it does
Text / Paragraph / Email / Hidden Compare normalized text using the database's case/accent-folding text equality.
Number Compare canonical numeric values: 01, 1.0 and 1 conflict.
Date / Time Compare canonical dates/times, independent of display format.
Dropdown / Radio Compare exact saved choice values, not labels.
Website / URL Compare the normalized complete URL; paths, queries and fragments remain significant.
Phone Ignore formatting punctuation under the provider's phone rules; international country digits are not guessed.

Entry status and corrections

Accepted entries reserve values; Spam and Trash do not. Restoring or promoting an entry to accepted status rechecks enabled duplicate rules and can fail if another accepted entry now uses the value. Editing an entry excludes that same entry from its own comparison.

An unchanged historical value does not need to be replaced just because an administrator edits unrelated metadata. Permanent deletion releases its reserved value, subject to other accepted entries.

Feedback and submission timing

Duplicate value message is plain text up to 1,000 characters; blank uses the default. The response does not identify the competing entry. The check runs on the server, not as a live availability request while the visitor types.

On a form with CAPTCHA, duplicate feedback waits until final submission passes verification. Other validation can still happen on Next. Do not use a hidden required unique value that visitors cannot correct without providing an appropriate workflow.