Hi there. Newbie here. On my dashboard, I have a collection (cards). Each of those blocks (cards) needs to connect to a different page or table. The only thing I have achieved is to have all the blocks go to the same details page. How do I set up each one to go to an individual form, details page or table? Ie This is what I need: I click on vet form and it takes me to the vet form, I click on collection lists and it takes me to my vet practices screen where again I have cards that each need to connect through to individual lists. Can someone please guide me on how to set this up. I have managed to figure a lot of things out and I need to find a way to get these all connected so that the app works. I don’t think it should be so hard to connect each card to its own action so it is also quite possible that I am missing something simple. Ultimately I want a dashboard which displays on mobile as 2 pics next to each other, as many rows as I need. Starting now with 4 but will need to add as I go along. I don’t mind using another method to achieve this but I don’t seem to be able to do it with images as I can’t put 2 next to each other. I am really open to any suggestions and happy to explain more if needed.
Thanks so much for reading.
Hi Kerry,
It’s not directly possible for each card in a card collection to perform a different action. To work around this, you need to create a new column in the Users table that stores a unique value for each item (e.g., Card, List, Vet form, etc.). These unique values must also be present in the table used by the card collection.
Here’s how it works:
Create an item click action that opens a new screen.
Add a Set Column Values action to update the column in the Users table with the unique value of the selected item.
On the new screen, place all item-specific components inside separate containers.
Use visibility conditions so that only the container matching the value in the Users table is displayed.
Example: If you select Vet form, the column in the Users table is set to Vet form, and the visibility conditions ensure that only the Vet form container is shown.
If this feels too complex, an easier option is to use Big Number components, since each Big Number component can have its own independent action.
An alternative to this is having different branches of logic for each value that the collection can have, and build different “new screens” for them.
Doesn’t scale well, though.