Beta feature
This is a beta feature, which means we're still developing it. Some functionality may change.
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 objects aren’t changed when updates move forward
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:
Navigate to the Development environment page. This is the environment intended for making changes.
Find the Resources section.
Select the app or pipeline you want to update.
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:
Finish making your changes in an app or pipeline
Return to the environment page
Select Publish
Publishing moves your updates to the next environment or directly to users, depending on your setup.