Sub tables

The Sub table field allows the creator to form a one to many relationship between two Datatables.

For example, A single restaurant receipt can have multiple items. A Datatable for receipts can use an Sub table for individual items. This forms the one to many relationship.

This is a powerful feature and should be used with discretion. You can have mulitple levels, however you should ensure you test for performance, to ensure your datatable design is scalable. You can also upgrade your Buzzy Deployment for more powerful infrastructure.

For each row that you render in a View (query) you can display the data and some related data from the row. The types of data you display includes:

  • the current row's data

  • linked table field's data

  • data from "parents" of the row

As an example, Let's say you have the following Organization -> (sub-table) Invoices -> (subtable) Invoice Line. Invoice Line includes a Linked Table Field to a Product so it can display it's name, image etc. If the current view is displaying Invoice Lines then if you add Organization Name (from the Organization parent datatable) and Invoice Number from the direct parents of the Invoice Lines, it will display those correctly. Again, this will require dynmically looking up that data, so use carefull from a performance perspective.


The target App and Datatable must be identified.

Last updated