I’m going through this right now. The issue I’m having is that I want inline lists drawing from the same table on multiple tabs, but with independent components drawing from different columns. But each time I put an inline list on a new tab, which draws from the same table as the other, the same components get pulled over as though each list is the supposed to be the exact same list. Are you doing something different? I tried different visibility options, but it gets messy.
Are you referring to the Title/Details/Captions for the Inline List component?
I have a method for having different values for each when viewing different inline lists of the same data.
It involves setting a user specific column in my user profiles table, and then using an if-then-else column to set my list title/details/caption (and sometimes image) depending on the value of that column.
It’s ugly, but it works. I’d be completely open to a simpler approach.
No, but I’ll keep that method in mind.
I have users and an admin using the same app. Within the app, to save on tables and rows, I went horizontal with extra columns instead (1000+). It still works pretty good with the inline lists. The next step is I thought that I would create separate tabs for the users and the admin, with row owners & a visibility control, and that works fine too. However, when I create an inline list on a tab for one set of columns, all of the components that I’ve applied to that table will be shown on all tabs with an inline list. It’s like I need the “independent screen configuration”, but per inline list. I started adding visibility controls for the components, but I’m not very happy about all the extra work.
This is what I was going to suggest. No great solution otherwise…unless one inline list is set to “show details” and the other is set to “show new screen”…not a great solution, but it might get you there.
Show New Screen is generally my go to method. Otherwise I find myself getting lost in a sea of components and visibility conditions. But I guess it depends on the complexity. Using visibility conditions isn’t too bad if there are are small number of components and only 2-3 different views.
We need component grouping!!
I’m trying this now as I haven’t used that feature before. I got way too far into building out the table before I discovered the front-end issue. Thanks
It’s a scheduling app, I have 7 x 24+ components per screen and multiple views.
Yeah, sounds like you should definitely give the Show New Screen method a try. It’ll be more screens to maintain, but each one will be lighter and cleaner. And copy/paste components takes care of a lot of the legwork.
Do you think there is a way to click on each row of the HTML table and have it open the detail view of that row?
I currently have an HTML list and then the same list as an inline list below to open each row.
Would be grate to just click on the table and not have this doubled
Maybe you can add another column and use href there to link to the deep link of the row?
However, I think it will mess up your flow a bit since I don’t think Glide can’t smoothly transfer the user to the destination screen like what you do for a “show screen” action, Glide will treat it like an “open link” action.
haha, you know what?
A client asked me to do exactly this for an app I’ve just started working on.
If the number of rows is fixed, then what you could do is make it several single row tables stacked on top of each other. You should be able to style it so that it looks like a single table. As each “row” would be in its own Rich Text component, each could have a distinct action. A lot of trouble, but it should work. Of course that wouldn’t work if the number of rows is dynamic.
I think what I’m going to do is make it so that when the table is clicked, it exposes an Inline List of the rows.
My table is dynamic
Its a workout program that the trainer writes in the app…
It works as far as getting a fresh canvas for components, but it breaks the link to “this item” for the details from the inline list. It just grabs info from the top row of the table, and I can’t filter the rows for the components, because it’s not an option.
I can set a USC column with the unique ID of the row before going to the new screen, but for a new screen there’s only a reference to the table to draw from. So I’m still picking away at this issue…
hmm, that’s not how it should work. Here’s a short video that shows an example of how I use it. Maybe this will help…
Yeah… I was doing something different alright because I failed to even see the tiny “this item” text as an option when creating the “new screen” action. When creating the action, the default data source shown was a Google sheet, and not the one that I was building on, so I quickly changed it to the sheet I wanted whereas “this item” is what I actually wanted…
Thanks for the demo, it was helpful.
It’s amazing and so beautiful. But I don’t understand all u usage.
Can u show a video with glide table and components?
I don’t have time right now, but perhaps I can put together a short tutorial in the next few days.
I really appreciate it!
Here you go…
On this wonderful winter evening, just know that somewhere in Russia right now, one person adores you and firmly shakes your hand.