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 will allow you to set up a custom view of blocks and actions however you wish, as if it were building another page!
Here are the some advantages of using a Custom Detail View for your data display blocks:
Full customization of blocks, actions and styling.
Contents can either be viewed as a modal or in a full screen without needing to leave your root page, making it more efficient to jump between records without needing to reload your page each time.
Clicked records will carry over their values into the custom view and can be readily referenced with the 'Detail' variable using the syntax {{detail.Field}}. Click here to learn more about this variable and how it can be used.
Example Use Case
Custom Detail Views are a way you can set up a "drill in" feature that can highlight a data relationship between two data sources. For example, you can have a Grid block displaying a dataset of Orders, and in your Custom Detail View, there's a table with a dataset of Products that are all linked to an Order ID.
When a record of the Orders Grid is clicked to open its Custom Detail View, it will store the entire record or row's worth of values including its Frontly ID.
Combine this field with the 'Detail' variable which can be passed into a hidden filter. For the Table block set up inside of the Custom Detail View, its hidden filter should look something like this.
If done correctly, your table should look something like this. Which will only show the products whose Order IDs (fueld not shown) match the Frontly ID of the clicked Order (from the Orders Grid).
Note: Basic relational data principles were used to facilitate this example in Frontly. Click here if you want to learn more about these concepts and how they can be applied further.