This section consists of Database Things and fields description for every thing which is part of the template.

Introduction

To get to the Data section, click the database icon on the left side tabs in Bubble Editor.

❕

See Bubble manual information when working with data: - https://manual.bubble.io/help-guides/working-with-data; https://manual.bubble.io/core-resources/data.

Data Types

☝

Note: In case you have accidentally deleted a data type - no worries! Bubble lets you restore💪the deleted data type. Clicking on ‘show deleted types’ or ‘show deleted fields’ from the Data → Data types tab will reveal the deleted items, and a ‘restore’ button will appear next to each deleted entry. Simply click ‘restore’, to restore a field or data type.

💡

Tip: Aside from the below-listed data types and fields, Bubble creates these default fields visible in each data type: Creator, Modified Date, Created Date and Slug, except for the User data type. The User data type will have the following fields: email, Modified Date, Created Date and Slug.

These fields’ values can be used in workflows, conditional formatting, etc. To learn more, see the Bubble manual

Booking

This object will contain information regarding the booking of an event. It comes with the following fields:

Field Name	Type	Notes
`Client`	`Client`	This field will store information about the user that booked the event.
`end`	date	This field stores the end of a booked event.
`Event`	`Event`	This field will store the event for which a booking was made.
`guests`	List of texts	This field will store a list of guest for the booking,
`note`	text	This field will store notes about a booking made by the host.
`start`	date	This field stores the start of a booked event.

Client

This object will store information about a client. It comes with the following fields:

Field Name	Type	Notes
`email`	text	This field will store the client’s email.
`username`	text	This field will store the client’s username.

Event

This object will hold information about an event. It comes with the following fields:

Field Name	Type	Notes
`active`	yes / no	This field marks an event as active or inactive.
`booking_interval`	number	This field stores the custom interval for a slot, if the even interval is custom.
`custom_interval`	yes / no	This field sets the interval of an event as custom.
`description`	text	This field is used to store the event’s description.
`end`	date	This field stores the event end date.
`host_email`	text	This field stores the host email.
`host_name`	text	This field stores the host name.
`host_username`	text	This field stores the host username.
`Invitees`	List of `Clients`	This field stores a list of invitees to this event.
`link_details`	text	This field will store a link that will open additional details about an event. For example, it can be a zoom link.
`minutes_after`	number	This field stores the amount of time after an event slot.
`minutes_before`	number	This field stores the amount of time before an event slot.
`name`	text	This field will store the event’s name.
`notice_amount`	number	This field will store a number which will determine the amount of time the user has before scheduling an event slot.
`Schedule`	`Schedule`	This field will store an event schedule.
`secret`	yes / no	This field will mark an event as secret, it will not be shown on index.
`start`	date	This field stores the event start date.
`Type`	`EventType`	This field will record the type of the event.
`valid_date_range`	date range	This field will store the date range of the event.
`valid_date_range`	date range	This field will store the date range of the event.

☝

Note: The data type has a privacy rule applied. See the 💬 in the database under the privacy section for details.

Exception

This object holds exceptions for a date. It comes with the following fields:

Field Name	Type	Notes
`date`	date	This field stores the date for which this exception will be applied.
`Exceptions`	List of `HourRanges`	This field stores a list of hour ranges, that will correspond to the actual exception you want to create.

HourRange

This object is used for storing hour ranges for a particular day within a schedule. It comes with the following fields:

Field Name	Type	Notes
`range`	date range	This field stores the range of hours.

Schedule

This object stores the scheduling information of events. It comes with the following fields:

Field Name	Type	Notes
`default`	yes / no	This field marks a schedule as default on signup. It cannot be deleted.
`Events_numbers`	List of `Events`	Counts the number of events for this schedule_pattern.
`Exceptions`	List of `Exceptions`	This field will store a list of exceptions for a particular day.
`Fridays`	List of `HourRanges`	This field will store a list of hour ranges for all fridays.
`Mondays`	List of `HourRanges`	This field will store a list of hour ranges for all mondays.
`name`	text	This field will store a schedule’s name.
`Saturdays`	List of `HourRanges`	This field will store a list of hour ranges for all saturdays.
`Sundays`	List of `HourRanges`	This field will store a list of hour ranges for all sundays.
`Thursdays`	List of `HourRanges`	This field will store a list of hour ranges for all thursdays.
`Tuesdays`	List of `HourRanges`	This field will store a list of hour ranges for all tuesdays.
`Wednesdays`	List of `HourRanges`	This field will store a list of hour ranges for all wednesdays.

Statistic

This object is intended to store information about subscriptions and the number of users subscribed. This object was created in order to enhance the speed of data visualisation. It comes with the following fields:

Field Name	Type	Notes
`count_user`	number	This field stores a number of users that correspond to the statistic type it’s being attributed to.
`Plan`	`Plan`	This field stores the plan name, for which it will count the users.

User

Bubble applications have a built-in User data type that acts like any type that is created in a database. For instance, you can modify a user, delete a user, list them in a repeating group, etc.

It comes with the following fields:

Field Name	Type	Notes
`12h_format`	yes / no	This field will determine wether the time on the platform will be shown in the 24/12 h format.
`admin`	yes / no	This field gives the user admin access.
`blocked`	yes / no	This field will determine if the user was banned from the platform.
`Bookings`	List of Bookings	This field will contain a list of bookings that a host has for his events.
`Country`	Country	Stores the user country.
`Events`	List of Events	Stores the events that a user creates.
`full_name`	text	Stores the user’s full name.
`ext_billing_period`	date	This field stores the next billing date for the customer’s subscription.
`Plan`	`Plan`	This field store’s the plan to which a user is subscribed.
`plan_schedule_cancel`	text	This field stores the scheduled api WF ID which is generated when a user wants to cancel his plan. This ID can be later used to resubscribe the user to the plan. If we want to resubscribe a user to the plan, we just cancel the scheduled api WF that cancels his subscription using the stored ID.
`profile_picture`	image	This field stores the profile image of an user.
`Schedules`	List of `Schedules`	This field stores a list of schedules created by the user.
`state`	text	This field stores a user’s state if he is from the United States.
`subscription_active`	yes / no	This field is used to determine wether a user has an active subscription or not, it is an auxiliary field, the app can work without it, but it can be used if you need additional customisations in the app.
`temp_email`	text	This field will store the temporary email of an user, for which the host decided to schedule an event.
`TimeZone`	`TimeZone`	Stores a saved user’s timezone.
`username`	text	This field holds a user username.
`welcome_message`	text	This is the welcome message of a host.

☝

Note: The data type has a privacy rule applied. See the 💬 in the database under the privacy section for details.

Variable

This is an object that holds template variables. It comes with the following field:

Field Name	Type	Notes
`access_rights`	yes / no	This field is intended to restrict a demo admin user rights, so that he doesn’t delete the template’s content.

Option Sets

💡

Tip: Option sets define a static list of choices for use in dropdowns, pop-ups, etc. Options inside the sets have at least a text display, but they can have additional attributes defined in the Data tab. To learn more, see Bubble Manual.

Below you can find the list of option set attributes and options.

Country

This option set holds a list of countries. It does not have any additional fields. It uses a built-in attribute to display the values.

The options for this set are:

Option

Notes

Afghanistan