Hi,
I added a new item to inventory yesterday and was able to select it to allocate to a project as per normal, but noticed one of my other items, shows up as Inventory and can be selected, but the Cost Per Unit for that particular item, cannot be selected.
I deleted that Item and added it again, but still, it shows as an Inventory Item, but you cannot select the corresponding Price Per Unit.
I thought maybe it was an issue with me having the item number limited, but I can’t see where the issue is.
The bottom two items are the issue, the one above is fine.
Ideas on what to check please?
Thank you
The source of the choice component is a column of the table where you are adding items?
Is there a reason you have to separate the cost per unit from the item? Is the relationship between item and cost per unit one to many?
I thought it would make sense to have a cost assigned to each unit and you can just do a relation - lookup but I want to know more about your data.
I tried it, but I couldn’t figure out how to get it to work properly, and this has been working until now.
I re-read your post. My question now would be are you adding a whole new item?
Or would you add the same item A multiple times if you want to allocate it to different projects?
I only add items once to Inventory and then allocate a portion of them to different projects. The same entry is in the screenshots because I was testing to see if there was an error on that line, or on similar descriptions etc.
Here’s my suggestion on the structure I would build.
Tables:
- Inventory Items
Create a master InventoryItems table where each row is a unique item you stock. This is the single source of truth for item meta: name, SKU, default cost per unit, and unit of measure. All selection in forms and screens should point back here via relations or direct references, not to duplicated item text in other tables.
- Projects
Use a Projects table where each row represents a project/job that can consume inventory. This keeps project metadata (client, dates, status, etc.) clearly separated from inventory data, and makes it easy to create project-level screens and summaries.
- Inventory Allocations
Introduce an InventoryAllocations table that sits between InventoryItems and Projects. Each row is “item X allocated to project Y with quantity Z at cost C”. In Glide, you’ll typically add rows into this table via:
- A form on a Project screen (writing a row linked to that Project).
- A Choice component to select the Item (backed by
InventoryItems).
- A computed or copied Cost Per Unit for that allocation (via relation/lookup or preset logic). You should never “select Cost Per Unit” as a separate entity. You select an Item, then derive or snapshot its cost into the allocation row. That avoids flaky behavior where some price rows show and others don’t, because price is always a property on an item or an allocation, not its own “choice source”.
Across the app, Glide relations and lookups do most of the heavy lifting:
-
Projects ↔ InventoryAllocations:
Project screen shows all related allocations via a relation column (one-to-many).
-
InventoryItems ↔ InventoryAllocations:
Item detail screen can show usage across projects.
Thank you for your help. All seems to be working now 
1 Like
