Thanks for explaining your idea. For this you don’t really need to create a separate collection for each shop; in relational databases (Adalo collections basically represent this approach) it is done in a bit different way.
What I could suggest reg. the DB structure:
- Shops collection, with the fields
- Shop name (text)
- Shop details (text)
- more to come (see below).
- Lists collection, with the fields:
- List name (text)
- Relationship to Users collection: 1:many, meaning that 1 user can have many lists, but each list belongs only to 1 user. Reciprocal field in Users will be created automatically.
- Relationship to Shops collection: 1:many, meaning that 1 shop can have many lists, but each list belongs only to 1 shop. Reciprocal field in Shops will be created automatically.
- more to come (see below)
- Items collection:
- Item Name (text)
- Item Description, price, … (what you need)
- Relationship to Lists collection: 1:many, meaning that one List can have many items, but each Item belong only to 1 list. Reciprocal field in Lists will be created automatically.
- NB: it’s possible to have other optional relationships for Items (to Users, for example), but it’s not necessary at the beginning.
After this, you might need to pre-populate the Shops collection with some entries.
With this structure, you’ll get the following:
- User can create a List, which will uniquely belong to a User and a Shop. So one user can have several lists for several shops.
- In turn, there could be several lists for each shop (belonging to different users)
- After creating a list, User can start adding the Items to this list.
I highly recommend to read documentation at https://help.adalo.com, especially the “Lists” section, so that you understand the principles off DB and app design better.
Hope this helps.
Best regards, Victor.