Hi everyone,
I’m building a data display app with a list page and a detail page. When a user selects an item on the list, the detail page should show a large number of different properties. — Over 100 fields.
Currently, I’m using blocks like:
set Label_A’s Text to get property “property_a” of object app variable ItemObject
set Label_B’s Text to get property “property_b” of object app variable ItemObject
…
However, as I add more blocks for each property, my project is becoming noticeably slower to edit and manage in Thunkable. The Blocks editor lags and sometimes even freezes, making development difficult.
Questions:
- Is there a more efficient or scalable way to display many different data properties on a single screen?
- Can I use functions or lists/loops in Thunkable to reduce block clutter?
- Any best practices or examples for managing this kind of layout in Thunkable?
Any tips, sample projects, or block screenshots would be greatly appreciated!
Thanks in advance!
You should use a custom Data Viewer List if possible.
Thanks~
Since the Data Viewer List displays all rows from a Google Sheet by default, is there any way to use it to display only a specific row (for example, the row that the user just selected on the list page), instead of displaying all rows?
If it can display only a specific row, how should I set it up? Are there any relevant examples or tutorials?
Yes, you can use a data source filter.
Hi, thanks for your suggestion about using the Data Source Filter and the “update filter for” block.
I did check the data source filter, but the “update filter for” block shown there is different from what I see in my Thunkable Builder.
In my workspace, the block is just update filter for [Data Viewer List]
without any place to set conditions (like where ID = ...
).
Here is what I set:
Is this a limitation of the free/builder plan?
Or is there something I’m missing to enable condition-based filtering via blocks?
Thanks again for your help!
Sorry, I should have linked to here: Data Sources | Thunkable Docs
Thank you for the clarification and for explaining how to use Filter Views.
From what I understand, Filter Views are set up directly inside the Data Source and can be selected in the DVL properties panel, but they’re static—you have to define the filter rules in advance.
However, my use case is to display a different row on the detail page each time, based on which item the user selects in the list. It seems that Filter Views are not dynamic enough for this scenario, since I would need to create a new filter for every possible selection.
Is there any way to dynamically filter the DVL to show only the row that matches the user’s selection, or is this limitation expected in the current Thunkable plans?
Or, is there a different best practice for showing a detailed view of a single row when there are lots of fields?
Thanks again for your help!
No, they are dynamic. Yes, you can set a filter view in the Data Source section but you can also create new filters using the Update Filter block. It’s shown on that same documentation page here.
You do have to set the key column(s) ahead of time but you can add any formula you want for the conditional block (text/numeric).