You can make this change in the sandbox application.
These updates will be applied to the live application.Note: This topic is for QuickBase Enterprise administrators only. If you have a QuickBase Team or QuickBase Extended Team account, you do not have access to this feature.
To make sure the changes you make in the sandbox application don't break your live application, QuickBase imposes some limits on what you can and cannot change.
In general:
You CAN add fields, tables, and relationships to the sandbox application. These new items will not be locked. You can change or delete any new, unlocked item in the sandbox application any time you wish.
You CANNOT delete locked fields, locked tables, and locked relationships from the sandbox application. (Remember that locked entities are entities that existed in the live application when the sandbox application was created.)
You CAN change most properties of both locked and unlocked entities in the sandbox application.
You CANNOT change the Field Type property for any locked fields in the sandbox application.
You CAN add, delete, and modify roles, shared email notifications, and shared reports in the sandbox application. You can also add reminders and subscriptions in the sandbox application.
You CAN add personal emails and personal reports in the sandbox application, but these will not be carried over to the live application after an update.
The following table illustrates the rules for making changes in the sandbox application.
You can make this change in the sandbox application.
These updates will be applied to the live application.
You can make this change in the
sandbox application, but these changes will not be applied to the live
application.
The QuickBase UI and API prevent you from
making this change. QuickBase blocks the sandbox update if it appears
you made this change.
Note: A change to the live application during sandbox development can make it appear as though you made a change that's not allowed. For instance, if you add a field to the live application, but not to the sandbox application, it will appear as though you deleted a field in the sandbox application. QuickBase blocks the update to the live application if this is the case.
QuickBase element |
Add |
Delete |
Modify |
Rename |
Application |
N/A |
N/A |
N/A |
|
Application properties |
N/A |
N/A |
|
N/A |
roles |
|
|
|
|
Application variables |
|
|
|
N/A |
Application pages |
|
|
|
|
Shared reports |
|
|
|
|
Forms |
|
|
|
|
Tables |
|
|
N/A |
|
Table properties |
N/A |
N/A |
|
N/A |
Relationships |
|
|
|
N/A |
Fields |
|
|
N/A |
|
Field properties |
N/A |
N/A |
|
N/A |
Field type |
N/A |
N/A |
|
N/A |
Key fields |
N/A |
N/A |
|
N/A |
Shared multiple choice source |
N/A |
|
N/A |
N/A |
Personal email |
|
|
|
|
Personal reports |
|
|
|
|
QuickBase imposes several cross-application restrictions in the sandbox application:
You cannot add new cross-application relationship from the sandbox application.
You cannot add a summary field to any cross-application relationship in the sandbox application.
You cannot add any cross-application permissions in the sandbox application.
You can indeed test shared multiple choice fields in the sandbox. Keep the following in mind:
You can create both the shared multiple choice field and the source field it refers to in the sandbox application. When you apply the update to the live application, the new shared multiple choice fields and source field will be added to the live application.
You can
create a shared multiple choice field in the sandbox application that
points to a source field in another unlocked live application.
Remember that you will also first need to go to the other application
and grant the sandbox application access to the source field.
You can then test the shared multiple choice field in the sandbox
application.
When you apply the update from the sandbox application to your locked
live application, the new shared multiple choice field will indeed
be added to the live application. Remember, though, QuickBase automatically
deletes the sandbox application after you apply an application update.
Because of this, you should remember to re-establish access to the
shared multiple choice field from the source field in the other application
The developer sandbox is a place where you can make and test application changes that could be risky or affect your data if you made them in the live application. Changes to personal or automatic emails aren't really in the risky category; changes won't affect your data.
Therefore, you shouldn't create a sandbox solely to test changes to emails. In fact, you won't be able to send automated emails from the sandbox application. Because lots of SPAM could be generated in an iterative development environment, QuickBase does not send automated emails (notifications, reminders, and subscriptions) from the sandbox application. However, you can create new automated emails in the sandbox application and use the Preview function to review the contents and appearance.