Views allow you to view and edit your database data in a more user friendly way.
Creating a view
You can create a view for a team or you can create a private view for yourself that you might later want to move into a team. You can do so from the main sidebar.
Once you’ve created your view, you will enter edit mode where you are able to configure details regarding your view such as:
- Show/hide/reorder attributes
- Specify sorts and filters
- Edit the name and emoji
- Pick the layout in which the data should be presented
This is where you will determine how your view displays a collection of records. You are able to do things such as:
- Decide if your view should be seen in table, list, or card layout
- Pick an attribute that is used for the display image on records
- Which attributes on visible
The single record configuration is how you want a single record to appear when it is selected in your collection view or when it is viewed through a view relation modal.
A relation can be used to show related records. For example, an ecommerce application might have an Orders view and an Order Items view. The Order Items view contains individual items that make up an order. By setting up a relation between the views, it’s possible to load all the items related to an order without navigating to the Order Items view.
View relations are accessible when viewing a single record and each relation shows up as a tab beside the Attributes tab.
Related records will display the first two list layout attributes for the related view. It will also display a display image for the record if it exists on the related view.
Nested view relations
It’s possible to click on a related record to view more details on the related record, including any further relations that might be associated with the related record.
The record creation form is what appears when you create a new record from your view or from another view that references the current view via a view relation.
The details section is where you can configure details such as:
- The name, description, and emoji
- Slack notifications
- What database tables should be joined to the source table in order to access more attributes on your view
If the source table used on the view has foreign key columns, then it’s possible to join the base table with other tables that correspond to the foreign key columns.
You are able to enable Slack notifications on a view from the details section in the view editor. When enabling Slack notifications, you must specify a “created at” date column that is used to determine if new records have been created. You can select the frequency at which slack notifications appear (daily, hourly, real-time). Note the real-time option concretely means that a check is done once every 5 minutes.