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.
Form Versioning Terms
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: For example, "Reverted from version 2" or "Migrated from pre-versioning"
Actions: Publish (revert), Edit (load as draft), or 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 edit form
- Click on the versions tab
Here you can see publish, edit, and view of all the previous versions of that form.
Now you can view, edit, or publish any previous version
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.
Exporting a single version
If all your submissions were made against the same version, or you only need entries from one version, select that version from the dropdown before exporting.
The resulting spreadsheet will have a clean, consistent set of column headers matching the fields in that version.
Exporting all versions combined
When you export all versions together, the spreadsheet includes a separate set of columns for each version of the form. This means:
- Fields that existed in v1 appear under v1 column headings
- Fields added in v2 appear under separate v2 column headings — even if they have the same name as a v1 field
- Fields removed in a later version still appear as columns, but will be empty for submissions made after that field was removed
This can make the spreadsheet appear to have duplicate or extra columns — this is expected behaviour, not a bug.
To consolidate columns:
- Identify matching columns from later versions
- Cut the data and paste it into the corresponding v1 column.
- Work left to right through the spreadsheet.
You can also filter by the version column in your spreadsheet tool to process each version separately.
📸 [Screenshot placeholder] — Annotated export spreadsheet showing: the version columns for each form version; cells that are empty where a field didn't exist in that version; and an example of consolidating v2 data into the v1 column.
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.
Viewing entries from older versions
If a form has entries from multiple versions, you can still view each entry individually. When you click into an entry, it displays with the correct fields and data structure for the version it was submitted against. The system automatically loads the right field definitions to show you exactly what the respondent saw and entered.