Navigation advice - tabs or sub menus or similar


Suspect there is no easy answer to this - but here goes!

In the absence of any submenu option in Glide - can anyone advise how to achieve the following?

Several projects in a project table. Users can choose a project which takes them to a detail screen with further details. Easy.

But I need to put a lot of detail on that detail screen - so ideally I would have pages added to the menu bar as necessary - or tabs or similar across the top (see screen shot from another no code builder I experimented with).

The tabs / buttons would need to be dynamic, as I will have a lot of projects and a lot of different information for each - so maybe a “TABS” table - with a list of available screens, and which project they relate to - or similar.

Any ideas - I started building it with lots of collections and visibility rules (Buttons writing to a user specific column in the user table as suggested in one of @Robert_Petitto excellent videos , but it gets complicated and messy very quickly.

Any suggestions welcome



Just a thought which came to me as I was making a cup of tea, but maybe I could -

  • Make a page for each type of info I need to display per project. Ie - a page for downloads, a page of comments.
  • set their visibility conditions so that tab only appears if a value appears in a table somewhere.

Then I can build each page exactly as I need

Granted the pages won’t be “sub menus” underneath the main “project” tab - but I think it would work?

We could really use something like this in Glide.

With Classic Apps it was relatively easy to get something like this using a segmented choice component and a bit of CSS. But we don’t really have that option any more.

I think a reasonably clean option would be to use a Collection as a menu. So one item in the collection for each of your “sub-tabs”, and then use a branching action that does a separate Show New Screen → This item for each one. This will give your 5 separate blank canvasses on which to build out your respective sub-screens.

It’s not an ideal solution, but it’s probably what I would do. Below is an example of the sort of thing I mean - what’s shown below is a single collection, but each item leads to a separate, independent screen on the same row.


Ya…button bar or choice component to write a value somewhere. Use that value as visibility condition for a container of components.

I asked Tristan a few months ago if we could have a tabbed “container container” so we could have this functionality natively. We’ll see if it ever makes it to development.


Thanks both

Will give each option a go on a test site I have. Realised I can’t add a screen (Tab) for the menu and add a visibility condition - as there is no way of setting visibility based on screen data :frowning_face:

@Darren_Murphy Can I just check as I don’t seem to be able to get it to work as you suggest.

On a detail page for the project, I have added a collection and set the source as a table called Tabs. Set as an XS grid so nice and compact.

In that tabs table, I just have for now the name for each of the 5 ‘sections’. So far so good.

I then enable advanced actions for that collection, and set the action for Item click to “Show new screen” and I set Data to “This item” and target as current.

I was kind of expecting or hoping to get a blank canvas with the “New screen” option - whereby I could lay the screen out how I liked - then I could lay out a separate screen for one of the other options. But it seems to just give me the same screen layout, but with the different data. I tested this by putting 'hard coded" text onto one of the screens - but of course it was identical when clicking a different tab.

I didn’t get the 5 separate screens you suggested in your post.

Or am I missing something?

Begs the question - what is the difference between Show new screen, and Show detail screen?

As always- thank you


You need a custom action that will open a different New Screen based on which item is clicked.

1 Like

Yes, what Jeff said :point_down:

Sorry, I probably could have made that clearer. My excuse is that it was late and I was frantically multitasking at the time :wink:


Sorry - I am either misunderstanding completely, or not explaining what I am after very well.

Was hoping I could have effectively 5 different screens, with a different layout and reading from a different table - all linked from one of 5 buttons or a collection with 5 items off a “Project” page.

I’ve added a collection of the 5 items - and added an action with a “Show New Screen” but that just opens a new screen for the current collection. I want a different page entirely for each of the 5 options.

Have I misunderstood your suggestions?

In the show new screen action you need some conditional branches for each show new screen.

E.g. if project equals 1 then show new screen
If project equals 2 then show new screen



Thanks all

1 Like

I would give a tip that works for me, change your 5 view name texts to a numeric field (1-5), so that If Name = 1, If Name = 2 etc are in your custom action.

And elsewhere enter the names for these and display them, that way all your functions still work if you ever decide to change the name (otherwise if you change PDF to PDF File) you have to go find all the actions where you wrote the plain text “PDF” and retype it to the new name.


Oh that’s a good idea. Good timing too as I was just typing them all in! Could save time later. Thanks

1 Like

Great :smiley: I’m glad you get it as well I didn’t have to go into more detail! Also if you ever do a similar thing with a choice component rater than a button, you can just write the numeric value of the choice but display the text value of that choice for selecting.

And if you have similar views across the whole app and want the choice to be the same (until changed) across all screens - write the choice to the User Field, so no matter where they go, the app knows the users current choice is Option 2 or whatever it may be.


Thanks again

Really pleased with what I have - and I think this is the final piece I needed to crack!

Could do with some better options / ideas for laying out the ‘tabs’ - this is what I have come up with so far - the tabs “PDF”, “Issues” and “Accommodation” take you to different screens.

The ‘Stacked version’ scales better on different screens but takes up a lot of space - and I don’t like the text spacing on the horizontal version. Going to have a play with icons - maybe heroicons could help!

Thanks again!

1 Like

One option would to make a single action row - don’t add a text or label or image, simply put your values in the action text name. You get a nice button alternative. You will notice buttons don’t change visually when you have clicked (unlike a choice), there are some tricks for this but - for now you set the currently viewed tab to an impossible action and it will render differently. For bonus points you can throw in an icon to the action!


Oh that’s a nice idea - and looks good too.

Only thing is, I have several projects and the tabs each project needs will be different for each one. They won’t all need the same tabs. The action row, I don’t think can be populated dynamically.

Using the Collection view, I can read the tabs from a table and add conditions to filter on project.

Still a nice option though - will definitely be using that somewhere.

On a similar subject - once a ‘new screen’ has been created - can it be linked to or referenced from elsewhere? I can’t find a slug or reference to it. I have seen options for “Link to current screen” - but can’t see that now. More out of interest than anything - wondering if there is a list of all pages / screens created somewhere

Yes and no. New screens are not as accessible as detail screens.

You can reuse custom actions, so if you call the same action elsewhere (with a New Screen action inside of that custom action), then I think you should get the same screens. I guess I’m not sure how that works with “this item” if you are calling the same action from different data sources.

On the other hand, a Detail screen is permanently attached to it’s source table, so anytime you use ‘Show Detail Screen’, you will get the same layout.


Ahhh - realised (after a lot of trial and error!) that putting a single button component inside a Custom collection - lets me do this. I can have dynamic buttons!

Thanks for the idea - just my bad execution that was at fault!


1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.