Please can you help me achieve this, tried two methods so far, one where 3 lists are snapped together on the favorites screen, this doesn’t look that good. And the other is one list, 3 details screens in one favorites list using visability rules, but this is hard work for a novice 
Hi @elainypeps,
Would you be able to share an example of what’s in the 3 databases?
Thank you and have a great day!
I think the way I’d approach this is a bit different and might simplify things for you.
I’d create a separate “Favorites” collection with:
-
A relationship to Current User
-
3 separate relationship fields → each linking to one of your 3 databases
-
A “type” field (e.g. db1, db2, db3)
Then on your Favorites screen:
-
Use one custom list (Favorites)
-
Inside it, have 3 containers stacked
-
Each container is set to show based on the type of favorite
So:
-
If type = db1 → show container 1
-
If type = db2 → show container 2
-
etc.
This works well especially if your 3 databases are quite different.
If they share similar fields (like title, image, etc.), you could actually simplify it further and reuse components instead of having multiple containers.
Not 100% saying this is the most optimal setup, but it’s a solid and scalable way to handle it 
You can always test performance using Adalo Xray once it’s set up.
Curious to see how others would approach it too — there might be even cleaner ways.
the databases contain different types of baby/child products
Thanks for the information @elainypeps! So you created 3 collections for 3 types of baby/child products? Maybe one collection to store the products and another collection to store the types, and both are connected with an one to many relationship? (for favorites, a m2m relationship or a separate join table to store favorites) Do those 3 collections share the same set of properties/columns or different properties/columns? Thank you and have a great day!
Hi Jeorge
Thank you for your help, please can you help with the following
Sure @elainypeps , which part do you want help with?