Forms keep a full history of every version you publish. You can edit a live form freely, test your changes privately, and only push them live when you're ready without disrupting responses already collected.
What is form versioning?
Draft: A form you're actively editing. Not yet live.
Published: A live form that's accepting submissions.
Version: A numbered snapshot (v1, v2, v3…) created each time you publish.
Test mode: A way to preview and submit a form privately, no entry is saved.
How versioning works
When you publish a form, infoodle saves a snapshot of it as a version (starting at v1). Every submission is linked to the version that was live at the time, so you always know exactly what the person saw.
When you need to update a form, you create a new draft. The current version stays live while you make changes. Once you publish again, a new version goes live (e.g. v2).
All existing forms were automatically set to version 1 when this feature was introduced, so no action is needed.
The Versions tab
The Versions tab gives you a full history of every version of the form.
Each row in the table shows:
- Version: v1, v2, v3, etc.
- State: Draft, Published, or Not active
- Date published / Published by: Who published it and when
- Field count: How many fields the form had at that version
- Notes: E.g. "Reverted from version 2" or "Migrated from pre-versioning"
- Actions: Publish (revert), Edit (load as draft), View (read-only)
The Versions tab only appears on the form edit screen not on the form list.
Reverting to an older version
You can load any previous version as a new draft.
- Click on forms
- Click on the pencil icon, the second icon on the right of the form row to edit
- Click the versions tab
- Click edit on the version you want to revert back to or straight to publish
Once published, you will see it now says "reverted from version #" in the notes column
Inherited (child) forms
If you use parent/child forms:
- When a parent form is published, all its child forms are automatically versioned to match.
- Any field overrides on the child (such as custom labels) are preserved.
- The child's version number increments automatically alongside the parent's.
- Exporting entries by version
When a form has multiple versions, the export dialog includes a version filter dropdown. You can export entries from a specific version, or from all versions combined. The version number is included as a column in all exports.
Version mismatch
If someone has a form open in their browser and a new version is published before they submit, they'll see a message asking them to reload the page. Their entry is not lost, they just need to refresh and resubmit with the new version.
Entries from older versions
If a form has entries from multiple versions, a warning appears at the top of the entry list:
"Some entries were submitted using an older version of this form. Their field data may not display in this list view. To see all fields, click on the entry to view it individually."
Clicking into an individual entry always shows the full field data for the version it was submitted against.