Iโm creating an inventory tracking app for a boutique hotel chain with 10 separate little 2-4 room buildings. The inventory in each building needs to be tracked separately, as if each building has its own โwarehouseโ of inventory.
If there were just one property this would be simple, but since there are 10 separate properties Iโm a bit stuck on the best way to do this in AppSheet. Would you create a separate inventory table for each property? Or would you create one inventory table, with multiple rows for the same item type (one row per property). Or would you structure it a different way that I havenโt thought of?
More along that route is what I would do.
I would create the following:
This way you can create the Inventory records as a sort of โMaster Listโ - then create the Property Inventory to keep track of whatโs actually there.
If you create a ref connection between the tables, youโll end up with a very nice list of related records for each property and inventory item.
Thanks @MultiTech_Visions โ Iโve attached an example picture below to ensure I understand what you are proposing. Is this what you were thinking? I have a few questions about this.
If I have to duplicate each item in the Building Inventory list then what is the purpose/benefit of having the Inventory table or the Buildings table? Genuinely curious if they would be used for anything.
Using this method, if I have to use pictures etc for each item, will I need to copy / paste the picture link to the item each time for a new property?
Seems that got cut offโฆ
With traditional database design schemas, youโll have these โsupportโ type of tables, where they provide you with a master list of options. Thereโs multiple benefits from this type of data schema, just a few of the main ones include:
Nice segue toโฆ
As you can see, with the parent-child reference connection youโll be able to input info into one record (like a photo) then just pull that info using a dereference when you need it again. The nice thing here is that even if you โCopy the image into a new recordโ the app doesnโt actually save a bunch of duplicates, it knows youโre using the same image and just pulls the one.
Awesome, thanks for the advice.
Youโre welcome! (^_^)
User | Count |
---|---|
32 | |
25 | |
24 | |
23 | |
15 |