Make changes in an environment

Use an environment to safely update your apps and pipelines before you release those changes to users. When you publish changes to the next environment, Quickbase uses the Quickbase Language (QBL) version your solution is set to. Each publish applies a full update of your entire solution.

QBL also defines how supported and unsupported schema behave:

• Supported schema follows the rules of the QBL version you selected.

• Unsupported pipelines and connected tables cause environment creation to fail when added to a solution.

• Other unsupported objects aren’t changed when updates move forward. Learn more about unsupported schema in QBL.

Move changes between environments

Always move changes to environments in the order of the structure you chose:

• Development > Production, or

• Development > Testing > Production

When you make manual updates directly in the Production environment, those changes are not tracked in the Development environment. This means that the next time you publish changes forward from Development to Production, the schema will be overwritten to match Development. This can cause untracked schema updates to be permanently lost.

To protect your work:

• Make schema updates in Development first

• Promote changes through the environment structure you selected for your solution

• Avoid making manual schema updates directly in Production

Following these steps keeps all environments aligned, allows for safe and repeatable deployments, and avoids accidental data or schema loss.

Open a resource to make changes

Each environment shows all the apps and pipelines it manages. To make changes:

1. Navigate to the Development environment page. This is the environment intended for making changes.

2. Find the Resources section.

3. Select the app or pipeline you want to update.

4. The resource opens in a new tab so you can update the structure of an app or pipeline. Live data is not included in the Development and Testing environments.

Your changes remain in the current environment until you choose to publish them.

Publish changes

To publish changes to another environment:

1. Finish making your changes in an app or pipeline.

2. Return to the environment page.

3. Select Review. The review modal may take a few minutes to load the changeset. Once it loads, you can:

   • View added, updated, or removed items

   • Search within the changeset

   • Expand specific apps, tables, or pipelines to understand what changed

   Use this view to confirm that the updates are complete, accurate, and ready to move forward. Learn more about limits to reviewing changes.

4. Once you’re satisfied with the changes, select Publish.

Publishing moves your updates to the next environment or directly to users, depending on your setup.

Limits to reviewing changes

There are a few known limits and issues in the Review changes modal. We’ll continue to develop this feature throughout the beta.

• Pipeline structures may not expand correctly when modifications are present.

• Rich Text page content is not rendered correctly.

• The changeset may display the AllowDataCopy property even when no actual changes have been applied.

• Phantom changes may appear in the changeset for legacy forms that contain rows with a single element.

• Some objects may be marked as changed despite no actual modifications.

• The changeset does not display changes for RoleDefaults and ReportOverride options.