What Can I Change in the Sandbox Application?

This topic refers to functionality that is only available to accounts on the Quick Base Platform or Quick Base Unlimited plans. If you do not see the functionality described here, either your account or realm has not been configured to show it, or your account is not on one of those plans.

To make sure the changes you make in the sandbox application don't break your live application, Quick Base imposes some limits on what you can and cannot change.

Rules for making updates in the sandbox application

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. Exception: Tables you add in the sandbox CANNOT be deleted.

  • 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 common 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

  • You CANNOT create a sandbox application for a connected app. Connected apps are Quick Base apps that have one or more connected tables.

 

The following table illustrates the rules for making changes in the sandbox application.

Key

 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 Quick Base UI and API prevent you from making this change. Quick Base 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. Quick Base blocks the update to the live application if this is the case.

 

Quick Base 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 (including app home pages, rich text pages, and code pages)

Common reports

Forms

Tables

N/A

Table properties

N/A

N/A

N/A

Connected tables

N/A N/A N/A

Relationships
(can delete if created in sandbox)

N/A

Fields
(can delete if created in sandbox)

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 value field source

N/A

N/A

N/A

Personal email

Personal reports

About cross-application relationships and the sandbox application

Quick Base imposes two 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.

About testing shared value fields in the sandbox

You can indeed test shared value fields in the sandbox. Keep the following in mind:

  • You can create both the shared value field and  the source field it refers to in the sandbox application. When you apply the update to the live application, the new shared value fields and source field will be added to the live application.

  • You can create a shared value 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 value field in the sandbox application.

    When you apply the update from the sandbox application to your locked live application, the new shared value field will indeed be added to the live application. Remember, though, Quick Base automatically deletes the sandbox application after you apply an application update. Because of this, you should remember to re-establish access to the shared value field from the source field in the other application

  • You cannot create a shared value field in the live app that points to a source in the sandbox application. In fact, you won't be able to select a sandbox application when you try to grant access to the source from the live application.

About webhooks and Actions in a sandbox app

You can add, edit, delete them in a sandbox app, however they won't run in the sandbox, even if they are set to enabled. They will appear in the original app when you apply your changes from the sandbox.

About emails in the sandbox app

The developer sandbox is a place where you can make and test app changes that could affect your data if you made them in the live app. Changes to personal or automatic emails 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, Quick Base does not send automated emails (notifications, reminders, and subscriptions) from the sandbox app. However, you can create new automated emails in the sandbox app and use the Preview function to review the contents and appearance.