Is it on a tab level or do you have any type of navigation before getting to that screen? If it’s the latter case, you can use a set column before showing the screen.
Not really much to it in regards to how I set up the tabs. The standalone tabs component is really just another type of choice component. When you select a tab (or make a choice), it writes that selection to a column in your table. All I’m doing is setting up visibility for other components on the screen based on that selected value in the table. Use the standalone tabs component like you would use a choice component.
Just a random Idea, how about u guys add a new style and make it the same as the choices component it’s so beautiful and I think I will be using a lot of it
It would only use updates if you have a legacy plan or you are using external data sources. Current plans that use Glide Tables do not incur updates for data changes in those tables.
Depending on your setup, there could be some roundabout ways to handle it. For example you could have a single row helper table that is a glide table, where you navigate to that screen and use it to handle your tabs in that glide table. If that screen needs to show values from a row in your google sheet, you could set a RowID in the helper table before navigating to the screen, and then use a relation/lookups to pull in those values. That’s kind of what I do with a custom Add/Edit form in one of my apps, so I know it works, but takes a little more setup.