# From Layout to Data – Seeking examples

**URL:** <https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268>\
**Category:** Ask for Help\
**Created:** [February 6, 2026, 11:31am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268 "2026-02-06T11:31:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [February 6, 2026, 11:31am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/1 "2026-02-06T11:31:05Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Ja\_ke](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ja_ke/32/83176_2.png) [@Ja\_ke](https://community.glideapps.com/u/Ja_ke)\
**Post date:** [February 8, 2026, 2:27am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/2 "2026-02-08T02:27:59Z")

</div>

Sometimes if i have a dashboard that i want to have collections and other fields from many different tables accessible in one screen. I often use a single row table with all user specific columns that once done, its an odd assortment of lookups, templates and queries.

I have always wondered if I was missing a better way of doing something when i had this.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [February 8, 2026, 8:03am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/3 "2026-02-08T08:03:00Z")

</div>

- A screen that needs a dedicated data source (thanks @Ja_ke)
- Reusable custom forms (thanks @Darren_Murphy)

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [February 10, 2026, 3:55am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/4 "2026-02-10T03:55:33Z")

</div>

A specific table layout. For example, daily schedules of available workers for the week.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [February 10, 2026, 6:48am UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/5 "2026-02-10T06:48:23Z")

</div>

Oh yes that’s a good one ! Not just a chart layout but also a specific table layout.

Thanks, Bob.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [February 12, 2026, 3:15pm UTC](https://community.glideapps.com/t/from-layout-to-data-seeking-examples/86268/6 "2026-02-12T15:15:44Z")

</div>

Consolidating just for reference:

(in no particular order)

1. **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.
2. **Custom filter**. Same idea.
3. **Generate chart & table layouts**. For instance yearly, quarterly, monthly, weekly charts and tables.
4. **Choice components**. A choice component sources the data from a general choices table or a specific table just that given component.
5. **Screen** that needs a dedicated data source.