Add and configure fields
Labels, keys, validation, layout, and field actions in Form Builder.
Video coming soon
Add and configure fields
id: academy-add-and-configure-fields · ~2–4 min
Audience: Admin
Every field you add from the palette opens in the property panel on the right. Configure these settings before duplicating fields or saving to production.
Label and help text
Field label is what mobile users see above the input. Write short, action-oriented labels (“Serial number”, not “Field 3”).
Help text (optional) appears below the label as a hint. Use it for format expectations (“Include area code”) or compliance notes—not for questions that belong in the label.
Static fields (Header, Paragraph) use the label area for their visible text.
Internal key (field name)
Each answer field has an internal key (shown as “Field name” / slug in the panel). Chekku uses this key in:
- Form response exports and reports
- API payloads and integrations
- Formula references
Chekku auto-generates keys from the field type (text_1, number_2, etc.). You can rename them to readable slugs (customer_name, qty_delivered).
Warning: Renaming a key after submissions exist breaks historical reports, dashboards, and API mappings. Treat keys as stable identifiers. If you must rename, plan a data migration or accept a break in continuity.
If two fields share the same display label, Chekku may warn about key conflicts—resolve conflicts before saving.
Required, read-only, and hidden
Required
Forces the respondent to answer before submitting the page or form. Use for compliance-critical data; avoid overusing on optional context fields.
Read-only
Disables editing. Useful for Signature fields filled from a preset variable, or showing calculated context. Read-only fields can bind to a variable key for pre-fill.
Hidden
Hidden fields stay in the definition and store values but do not appear to respondents on mobile or in PDF output. Chekku uses hidden fields for auto-generated correlatives and similar backend-managed values. Do not rely on hidden fields for questions users must see and answer.
Column width
Choose Full (12 columns) or Half (6 columns) width. Two half-width fields sit on one row on desktop. On mobile and narrow editor widths, half-width fields stack to full width automatically.
Pages
Multi-page forms show one page at a time on mobile. Assign fields to pages from the canvas page tabs or by moving items in the outline.
Use Move to page / Copy to page actions on a selected field to reorganize without re-creating fields.
PDF page break
Enable Page break before on a field to force a new page in PDF output. Place breaks before major sections (sign-off block, terms) rather than every field.
Replace field type
Click Change type on a selected field to swap its element (for example Text Box → Number) while keeping label and key when possible. Chekku warns if the replacement drops options, formulas, or data-source bindings. Radio ↔ Checkbox swaps usually keep option lists.
Review the canvas after replacing types—validation and visibility rules may need updates.
Tips
- Set internal keys once, early in the build, before pilot submissions.
- Pair half-width fields that belong together (city + postal code).
- Put page breaks at natural section boundaries, then verify in PDF preview.
- After changing keys or types, open Mobile preview and submit a test on a phone.