Skip to main content
All CollectionsBasics
Detail View (Default and Custom)
Detail View (Default and Custom)

Understanding the differences between these views.

Justin Yan avatar
Written by Justin Yan
Updated over 3 months ago

Default

By default, all Blocks that display a list of records (Table, Grid, Chart, Kanban, Map and Calendar) have a built-in Detail View, allowing users to click on a specific record and view/edit that information.

This setting is turned on by default but can be disabled by changing the 'Record Click Action' setting.

The edit and delete function can be disabled by toggling off the 'Allow Editing Records' and 'Allow Deleting Records' settings, respectively. This turns the default detail view into a expanded list of text field, labels and their values with no editing or deleting functionality.

Click here to learn how to customize your Default View.


Custom

If the default detail view is too simple for your needs, you can change the Record Click Action to 'Custom View', which allows you to define a set of Blocks to appear on record click instead of the Default View.

Important note: Blocks defined here will have access to a 'Detail View' data source which contains the data from the record that was clicked to trigger this popup. The majority of the time, this feature will be used to display another list of related records, but filtered by the clicked record for relevance.

Example: You have a Grid block displaying a list of Orders. In your Custom Detail View, you add a Table block displaying a list of Products in the clicked order. To set this up, you add a Hidden Filter to the Products Table 'Order ID Equals Active Record ID'. With this simple setup, you have a functional app displaying your orders and on order click, a popup displaying all the items in that order.

Note: For the above example to work, you need to ensure you have two separate spreadsheet tabs with fields associating the records. In this example, the Orders spreadsheet would have an ID column and the Products would have an Order ID column.

Click here to get a better understanding of Relational Data and how to set up Relational Fields in Frontly!

Did this answer your question?