Sometimes, you want users to click on items in a collection and be taken to different pages depending on what they select. This can be useful for creating dynamic experiences—like a menu that takes users to specific sections, dashboards, or detail views—all from a single collection list.
Here’s how you can do it:
Step 1: Create a New Table for Navigation
Start by creating a new table. This table should include a list of the items you'd like to show in your collection (e.g., Contacts, Companies, or Topics). In this table, make sure you include a Page Name that indicates which screen the item should navigate to.
Step 2: Set Up a Collection Component
In your layout, add a collection component using this new table as its data source. This will display the items to your users.
Step 3: Create a Custom Action for Navigation
Now, set a custom action for the collection. Here's what you need to do:
Select Actions in the collection, set the item click to create a new workflow.
Add multiple branches using "If condition".
For each condition, check the value of the Page Name column.
Example: If Page Name is "A", then add "Go to Tab" action → Page A.
Repeat this for all other page names like B, C, etc.
This way, clicking on each item will route the user to a different screen depending on its configuration in the table.
Step 4: Test and Tweak
Make sure each page you reference (A, B, C...) is already created and added to your app's tab list. You can now test your navigation to ensure everything works smoothly.
Understanding "Details Screens" and Custom Views
Keep in mind: Glide allows only one Details screen per row of data. So if you're hoping to create different views for the same row, you won’t be able to configure separate Details screens directly.
Instead, use the "Show new screen" action, which opens a completely independent screen when an item is clicked. This is useful if you want to create multiple unique layouts or flows from the same row of data. (In Classic Apps, this was previously available as a built-in option and is now handled manually via actions.)
Try the Live Example
Want a ready-to-use example? Check out this live template you can copy and explore:
👉 Click here to view the template