Use tables to view your data. Tables are a key component within many tools, allowing users to search and manipulate its data, while also providing its data as inputs to other bound components, like forms and buttons.
When a user selects a row in a table, the data in that row can be used as inputs for components like buttons, forms, pop-up forms and dynamic buttons. This is done through Field Configuration (within the non-table component).
When a user selects a row in a table, the data in that row can be used to filter components like card lists, detail views and even other tables. Use the filters for that component and choose to compare against data coming from a selected table row.
A number of components can be inserted into a table - these components appear in every row and typically perform functions either using or changing the data in their row. You can add buttons, pop-up forms, dynamic buttons, calculated fields, s3 uploaders, links and images.
First, select the resource whose data this table should show. Your table name is shown at the top of the component.
You can set filters to change what's displayed in the table, based on your criteria. Click “Add filter” to add your first table filter.
Each filter has a table field which is compared to a value. A preset filter compares against a fixed value, whereas a dynamic filter compares against data from another component. Dynamic filters are another way to bind components together to add functionality.
Preset filter example
You have a table of Users which contains users with both "Active" and "Suspended" status. You're creating a tool to reinstate suspended users, so you want to only display "Suspended" status users in your table. You set up the following filter: status [is equal to] suspended .
Other examples of preset filters:
Dynamic filter example
Let's continue the example above of an on-demand service with a Riders and Rides table in the space. You want to make it easy to look up the rides for a given rider - the two tables are linked by a foreign key; the id column in the Riders table matches with the rider column in the Rides table.
You create a filter in the Rides table as such:
This would bind these two tables together, so that whenever a user clicks on a rider in the Riders table, the Rides table is filtered down to display just that rider's rides.
Just like binding two tables, dynamic filters can also bind a table with a filter, detail, or card list component:
Here you can rearrange your table columns and remove columns. You can also customize how your data in the table is displayed, using icons, pillboxes, or links. The "autolink" option appears for fields that are a primary key and will turn this into a link to the Super Record.
Clicking “+Add Column” at the bottom will allow you to add back any fields that were removed. This will also allow you to add inline buttons, dynamic buttons, pop-up forms, calculated fields, s3 uploaders, links and images to your table.
If you don't want a user to see a data column, but still want to use its data in other components, remove the column and add it back as a hidden field.This means the column won’t be displayed in the table, but you can still use the data in the column as inputs for another component.
Users in this space can still re-sort the table; this setting determines the default sort order.