The App Data section in the Data Tab shows the application database, i.e., the actual data that you or your users have entered. Keep in mind that the Live and Development versions of the app have different databases.
When looking at the user table, clicking the button 'Run as' runs the app as if you were that user, which makes debugging particular cases much easier.
Warning: Until you logout, you are using the app as this user, so do not make modifications.
Clicking this button displays a popup that creates a new database view, which defines the fields that are seen on the right side of the screen. Constraints can be added to create a smaller list. By default, each type has a view that shows most fields with no constraints. The number of views is unlimited, and these views are shared between the Live and Development versions.
Click the "Copy" icon next to the name of an existing database view to create another view just like it. You can then modify and add additional constraints to the duplicate.
Enter something into the input box, and the things in the current view that contain the entered text are listed. Use this for a quick search of the app data.
Clicking this button displays a popup where you create a new database entry. Choose the type of thing and enter information into the predefined fields. This is equivalent to using a 'Create a new thing' action in a workflow.
Clicking this button displays a popup where you upload a comma-separated CSV file of data. The type of data and relevant fields should be defined in the app before importing the file. This feature is available to users with a paid Bubble plan. Select the type of data and file to upload. Map the columns from the file to the fields of the data type and then validate and upload the data.
Important: The first row of your CSV file must be a header row containing the names of the fields for the data. Here's a sample file for reference.
You can bulk-modify data via a CSV upload. To do so, you should have a file with a column containing the unique ID of the things you want to modify, and enter the values that should be modified in subsequent columns.
This button generates a CSV file with the data of the current view. The file is exported to the Download folder of your browser. This file can be edited. Because the app owner performs this operation, no privacy rules apply, and all fields chosen in the current view are exported. This feature is available to users with a paid Bubble plan.
Clicking this button displays a popup that runs an API workflow on the entries in the current view. This is useful when you want to modify a list of things in the database. Select the API workflow you want to run. The workflow takes only a thing as a parameter.
Warning: This operation permanently modifies the data. If processing many entries, this may take some time.
Clicking this displays the Version dropdown menu to switch between the Development and Live versions of the app. Remember that each version has a separate database.
Clicking this button opens a popup to overwrite the Live version of the data with the Development version, and vice and versa. Use this to test the app with real data or migrate the Development version data to the Live mode. For users with a paid Bubble plan, the application database can be restored to an earlier point in time. The restore functionality is designed to recover from mistakes that corrupt or delete big chunks of data. It restores the complete state of the database, including all the users' account information, a list of images, scheduled workflow runs, etc.
Warning: Any data created after the restored version will be deleted. This option should be used only in catastrophic situations where it is better to revert to a previous database than to work with the current database. Restore operations are reversible. Simply perform another restore to the point in time right before the first restore.
Clicking this button opens a popup where you define the primary field for each of the data types. This determines the way the data is displayed and how the CSV files are generated. For example, a user may be represented by his email, an apartment, an address, etc. This is for display purposes only.
Refresh to view recent changes to your data, especially as the result of a backend workflow or database trigger event.
Click here to display an additional 50 rows in this database view.