Solution versioning

Access to this feature can change based on your Quickbase plan. Learn more about feature availability and plans in Quickbase capabilities.

Solution versioning allows you to create snapshots of an entire solution and restore a previous state when needed.

Versioning applies to:

• All apps and pipelines in the solution

• Schema only (not live data)

Use versioning to protect major changes, recover from deployment issues, or preserve known-good states.

Create a version

Create a version before making significant structural changes or publishing updates.

1. Open Solutions

2. Select a solution

3. Select New Version

4. Enter a version name and description

5. Save

Each snapshot captures the schema of:

• All apps currently in the solution

• All pipelines currently in the solution

Up to 30 versions can be stored per solution.

Version snapshots are stored within the solution and can be viewed at any time.

Understand what a version includes

A version snapshot captures:

• Tables

• Fields

• Forms

• Reports

• Relationships

• Pipeline structures

• App settings

Versioning does not capture:

• Record data

• Plugin configurations—If a solution includes plugins, restoring a version removes the link to the plugin from the app.

Restore a previous version

Restoring a version replaces the current solution schema with the selected snapshot.

1. Open the solution

2. Open the Versions list

3. Select a version

4. Select Restore

5. Review the comparison and select Next step
   

6. Confirm restore

The restore process affects the entire solution. You cannot restore a single app or pipeline independently.

Note

During the restore process, the pipelines in the solution will be in edit mode, which means they will not be executed during that time (similar to if you enter a pipeline to edit it through the pipelines designer). The restore process may take a few seconds.

Review schema differences before restoring

Before completing a restore, review the comparison between the current solution schema and the selected version.

Important behaviors:

• Apps or pipelines deleted after the version was created are not restored.

• Apps or pipelines added after the version was created remain in the solution but are not rolled back.

• If tables or fields exist in the current solution but not in the selected version, restoring permanently deletes all data in those tables or fields.

• If tables or fields exist in the selected version but not in the current solution, they are recreated during restore (no historical data is restored).

Warning messages inform you of any of these scenarios:

Restore restrictions

You cannot start a version restore when there are no common resources (apps/pipelines) between the current solution and the selected version. If you try to restore a version with no common resources, an error message displays and you cannot proceed with the restore of this version.

Delete a stored version

To delete a stored version:

1. Open the solution

2. Open the Versions list

3. Select a version

4. Select Delete

5. Confirm deletion

Deleting a version permanently removes the snapshot.

Use versioning alongside environments

Versioning and environments serve different purposes:

• Environments control how changes move forward (Development → Testing → Production)

• Versioning allows you to preserve or restore a snapshot of a prior schema state

Versioning does not automatically revert a publish. If unintended changes are introduced, you must manually restore a previous version.

Restoring a version affects the entire solution across environments.