General discussion here.
Most of the time in Glide, it’s wise to start with the data in mind and then to build the layout. Here, the data determines the layout.
But sometimes, it is a specific layout that drives a specific data setup. For example:
- A custom form. This specific layout requires a single-row helper table. That single-row helper table wouldn’t “naturally” exist in the database schema if it weren’t for the custom form.
- A custom filter. Same idea.
- Yearly, quarterly, monthly, weekly charts.
- Choice components. A choice component sources the data from a general choices table or a specific table just that given component.
What other examples come to mind?