FIELDS

Name field

Configure Logical Forms Name inputs, choose first/middle/last parts, set each part's label and requiredness, and use structured answers in entries.

3 min read · Updated November 19, 2026

Use Name when first, middle and last names should be available separately within one question. The whole field has one identity, while its fixed input keys keep the parts structured for entries and merge tags.

Availability: Core (Free).

Add and configure the field

  1. Open the form in Build and add Name from Add fields.
  2. Select its canvas card to open Field options, then configure the controls below.
  3. Save the form and check its saved Preview and embedded page.

Field-specific settings

Setting What it does
Name inputs First name and Last name start enabled; Middle name starts disabled. Expand each input to set Label, Placeholder, Description, Default value and Required. Enable or disable the part with its switch. At least one part must stay enabled.

Applicable shared options

This field also provides Description placement, Validation message placement, Sub-label placement, Label, Description, Required message, Invalid value message, CSS classes, Hide label, Admin label, Visibility. See common field options for their behavior.

Review Visible, Hidden and Internal before changing presentation. Static hiding differs from conditional applicability.

Dynamic population offers Disabled, Parameter, Current user. Parameter name binds an external URL or embed value. Submitted or cleared answers are not refilled.

Answers and behavior

Requiredness is set on individual enabled inputs. The parent required marker is derived from those flags; there is no second independent Required checkbox. For example, require First name while leaving Middle name optional.

Drag input rows, or use Alt plus Up/Down on their handles, to change display order. Reordering does not change the first, middle and last identities. It affects the whole-name display while part-specific tags still refer to the same parts.

Per-input labels are required. Text settings support up to 255 characters and descriptions up to 1,000. Each submitted text part has a 255-character limit. Default values apply initially; they are not replacements for missing or cleared submitted parts.

The entry stores a structured first/middle/last answer. Whole-field output formats the name in the configured order. Use a tag such as {field:5.first} for a particular part, replacing 5 with your field ID. Known historical disabled parts remain readable rather than being erased by a layout change.

Example and checks

For Your name, enable First name and Last name, expand each and select Required. Leave Middle name disabled unless your workflow needs it. Use descriptions sparingly so the field remains easy to complete.

Test an empty required first part, a complete name and a reordered display. Current user dynamic population can map enabled first/last parts automatically; it keeps the configured middle fallback. Test that signed-out visitors see the intended defaults and that populated names remain editable.

Check both the formatted full name and component values in the entry. Use the field-level custom messages to explain errors while retaining the input-specific correction targets.

Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.