Save to database
Overview
Save to Database stores submitted entries so you can review them later in reporting and export workflows.
Why it matters
- Enables entry history and auditability.
- Powers reporting dashboards and exports.
- Supports spam review and cleanup workflows.
Setup
- Open the Form module in the Visual Builder.
- In the Content tab, enable Save to Database. See Save to Database on the Form module.
- On each field you want stored, leave Show field in Entries Table? on. See Database Entries Option.
- Submit a test entry and confirm it appears in Form Entries.
Field settings for saved entries
Each Form Field has a Database Entries Option group in its Content tab. Use it to control that field in saved entries. Step fields do not have this group.
- Show field in Entries Table? — on by default. Turn it off to leave the field out of saved entries.
- Header Title in Entries Table — column name in the entries table. Blank uses the field title.
- Is Single Checkbox Field? — for a checkbox with one on/off option.
- Alternative Single Checkbox Value — value stored when that single checkbox is checked.
- Show Image? — for file and image fields, show the image in entries instead of a link.
Setting details are in Database Entries Option on the Form Field module.
Verify it works
- New entries appear in Form Entries.
- Export includes the expected test record. See Export data.
- Spam and flagging workflows can see saved entries. See Spam management.
What's Next
- Review saved submissions in Form Entries.
- Adjust columns and excluded fields in Database Entries Option.
- Configure Spam flagging for moderation workflows.
- Configure Field mapping if saved data should also map to post or user data.