Creating, saving and deleting data
This article covers how to work with the data in your database by creating, changing and deleting things
Last updated
Was this helpful?
This article covers how to work with the data in your database by creating, changing and deleting things
Last updated
Was this helpful?
Bubble comes with a range of different ways to work with the data in the database to:
Create new
Make changes to existing things
Deleting things
Manipulating data in the database is done in three different ways:
You can set up that trigger on specific events, such as the user clicking a Save changes button
You can use to save changes in the database every time the user provides some input to an
You can edit data directly in the database using the . This option is only available to users who have that access in the Bubble editor
A workflow is a collection of actions that run in sequence whenever an event happens. You can choose between many different types of events, such as a button click, an input field being updated or when a specific condition is true.
There are few different actions that make changes to the database. You can click the links below to see the core reference entry for that action:
Create a new thing: creates a new record of a specific data type and optionally saves information in the fields of that data type
Make changes to a thing: saves new information to a thing, replacing whatever was in the field before
Make changes to a list of things: same as above, but works on multiple things at once.
Make changes to the current user: the same as above, but works directly on the user that started the workflow
Delete a thing: deletes a thing from the database
Delete a list of things: same as above, but for multiple records
Copy a list of things: creates an identical copy of a list of existing thing with a new unique ID and updated Created date and Modified date fields. You can copy up to 50 things in one operation.
By combining these actions in various ways, you can work with new and existing data in a flexible manner, and even include additional actions that are related or unrelated to the database.
Let's say you have set up a form that lets a user edit their own profile. In that case we would have some different input fields that let the user provide information. We could then have a button that triggers the workflow:
The setup above would mean that no changes are saved to the database until the user actually clicks the button.
Note that some information, like email and password, has to be changed using a different action from the Make changes to thing. Because of the sensitive nature of user credentials, it's necessary to handle them differently to ensure their security and protect user privacy. Article: User accounts
Using workflows let you set up additional actions after the first one to perform other relevant tasks. For example, we could use the to display a message that the operation was successful:
As we can see in this example, workflows are useful when you want the user to be able to decide when to save the changes, and if you need to chain more than one action in the workflow.
Auto-binding means to bind an input element to a specific field on a data type. When this is set up, Bubble will automatically save any changes made in that element to the database. This means that you don't need to set up any actions to make the changes.
Auto-binding is connected to a field, meaning that the data format of the input element and the data field must match: for example, a field containing a date must be connected to an input element that expects a date from the user.
Also, auto-binding will only work if the parent of the input element has a and it cannot create new things: only write to things that already exists.
In the example above we have set up a that automatically saves the input to the Name on the user. The user is , which either a or itself.
The data is saved whenever the element loses focus, meaning that the user has clicked or tabbed away from the input field. Bubble will display the loading bar for a brief time to show the user that the data is being saved.
Note: Auto-binding on an input will run immediately, rather than waiting for the "next step" when using the step-by-step feature in the debugger.
When auto-binding is active you can show an alert to notify the user that it was successful. To use this feature, you need to first place an alert element on the page. Checking the Show an alert on success lets you select which Alert element to use and what message to show.
In the screenshot above you see we have created an alert element and checked the Position the alert at the top box to make sure it's displayed as a full-width bar at the top of the page.
On the input that has auto-binding activated we pick the alert element we just created. We also created a custom alert message that coincides with the field that was changed.
There are some key differences when choosing to work with workflows or auto-binding:
The first is simply how it affects the user experience. In some forms it makes sense to let users review their information and not save anything until they click a button. In other cases it's more efficient to save the information as soon as the field has been edited. It's up to you as the developer to decide what's best in each case.
Bubble handles security on actions and auto-bind a bit differently:
Workflows are not affected by and need to have their own conditional expressions set up to control who can do what. As an example, in the action below we have set up an expression that dictates that a user can only edit a profile if it's his own:
Auto-binding has a dedicated privacy rule which dictates under what circumstances changes to the field will be saved. The field will still be editable, but when it loses focus it will generate an if the privacy rules doesn't allow for the user to save changes via auto-binding.
In the screenshot above we have set up a privacy rule that allows the Name field to be edited if the user being edited is the same as the current user. If someone else tries to edit this user with auto-binding, it will generate an error message.
Workflows and auto-bind also has a slight difference in how they behave from a performance perspective:
Workflows sends all the changes that need to be made in one big chunk to the server. This means you will have fewer slowdowns, but the one you have may be longer, depending on how much data is transferred
Auto-binding sends the updated information to the server immediately when a field is edited. This means you will have more, but possibly shorter data transfers
There's no right or wrong answer to what the right approach is. Also, it's important to note that the difference can be very small, often negligible. While the difference is there, it's important to weigh the pros and cons in terms of the total user experience to decide what method is best.
Bubble also lets you edit data directly in the built-in database editor. This works both for the Development database and the Live database.
You access the database editor by going to the Data – App data tab and selecting the data type you want to edit. You can search for specific things and edit them by clicking the edit icon.
Editing directly in the database is useful when you need to make a quick update, but as a long-term solution we recommend setting up your own forms to edit data.
Yes. You can set up a workflow using the An input's value has changed event and place additional actions there. It's worth noting that the auto-bind operation may or may not have finished in time for the action to register the change. In other words, if any of the actions in that workflow rely on the data having been saved to the database, you may want to save it in a workflow instead of auto-binding. That way you can ensure that the process has completed by using the Result of step X data source.
Auto-bind only works on existing things, and cannot create new ones. If you try to write something in a container that has no data loaded, the operation will fail without showing any errors.
