Complete novice to Appsheet here. I have searched for days for a solution. I have created an app with the Inventory management template. I customized within the app and exported as previous attempts to create the app from existing spreadsheets failed. Everything is great, almost! I have 7 items that make a “kit”. The 7 items will not be “sold” individually. The “kit” will not be “purchased”.
I cannot find a way to automatically deduct the inventory counts on the 7 items that make the kit when a kit is sold. Vice versa, I cannot find a way to automatically increase the inventory of the kit when the 7 items are purchased.
Example: Items 1, 2, 3, 4, 5, 6, 7 = Item A When Item A is sold I want items 1-7 to decrease inventory count. When items 1-7 are received I want to increase inventory count for item A.
The formula currently used in google sheets to accomplish this are not transferring to appsheet correctly.
Any help would be incredibly appreciated!! Thank you!
Since you are a novice, we can’t be sure what level of understanding you might already have. Some of the below may be difficult to follow. If it is just respond and let us know.
The issue you are likely facing in AppSheet, is that by the time you have navigated through the succession of actions to finally update the Inventory Row, you no longer have access the Order details to get the count to update with. About right?
AppSheet has introduced the INPUT() function to help plug this gap. It works well if it available to you. This feature is still considered in Beta but if you have access to it, it will help solve the above mentioned problem. Check out the linked article to understand how to use it. It is relatively simple.
If you do not have access to the INPUT() function, then you will have to come up with a creative way to gain access to the changed values to apply to the Inventory row. There are basically two approaches:
-
Use a timestamp to identify the just changed row in your order source. In the Inventory row update action, use a SELECT() that identifies the just changed row and grab its quantity to adjust the Inventory with. In this approach, it is assumed the latest changed row is the correct one.
-
Personally, I don’t like to rely on assumptions and in some use cases the app simply cannot rely on the latest changed row. To avoid the assumption, the app needs to declaratively identify the exact row that has changed. To do this, there needs to be a way to “remember” the changed row. I typically do this by building a table to temporarily remember the row that has changed and then use this table to identify the exact row to access when performing the Inventory row updates.
If the issue you are facing is different. please elaborate. Ask if you have any questions. I hope this helps!