Logging product "loads"

[AGairAdmin]

quick breakdown 

when a crew takes product from a source we want to track that event for that work order, that work order can have many "loads" taken and we would like to log all of the "loads" 

above is the table with headers we are planning on using
Task in order of importance listed below

1. for each "load number" should be a new row
   1. currently it is updating the same row, and the counter goes up

so right now the it shows , load number "6" and it was qty of 14 
the goal is ... 
to click on / open a work order 

add loads as they take product 

have each "load" logged 

and to display the current total of product used calculated by the load

 

the above screen capture shows how it currently appears in the "app" 

if i want to add a load to the current order we have to click on the row, then click the edit icon , then adjust the amount 
the counter goes up by 1 , and back on the main page it shows the last load counter number, and the amount for that load , 

when i go to the DB table it too only shows the last edit/entry see below 

 
if we can get each load to log on a new row that would be a win for us. 

this is a part of a larger system, work order keys, will reference another table right now its just not connected for testing 

[Marc_Dillon]

What is your question?

[AGairAdmin]

what we want (new row for new event)
load 1 (counter)  // amount // date time 

load 2 (counter) // amount // date time 

load 3 (counter) // amount // date time 
---------------
what it is doing (updating same row) 
load 3 (counter) // amount // date time 

we are losing the logs of what the previous load was, with current set up, if load 2 was 25 gallon when you put in load 3 the data for load 2 is overwritten 

[Lynn]

Hi @AGairAdmin 

• Have you tried making the loads a child table of  the order?

[AGairAdmin]

we have not yet, just running to this issue, ive read and watch several video from appsheet youtube page. 
i have a orders table that this will reference.
learning as i go. there a many parts to the whole ecosystem , here is a list of tables ive already created, non of them have function, its just headers of the info need.

Boundary  // WO main // order chem // order comp // order weather // load counter // company // equipment // users

WO main = order key / order id / order active version / order status  etc... it houses the main work order identifiers

i like your horse by the way !!

PS this is an agricultural software product in the making, 10 years of telling the others companies how to improve software and being ignored equals us making our own lol 

[Marc_Dillon · Accepted solution]

"if i want to add a load to the current order we have to click on the row, then click the edit icon , then adjust the amount "

Because you're editing the old record. You need to add a new record.

[AGairAdmin]

using the same set us as it is, how do i add a new record? , when i tried to it would not allow the use of the same work order id , or work order key, it required making a new work order key or work order id

[Joseph_Seddik]

If you need to maintain a log for your loads, then you have to create a table for your Loads. Automation will trigger on the creation of a new "Loads" row, to update the corresponding workOrders row accordingly. 

[AGairAdmin]

would you say a good process is for each primary table there should be a "child log" table?

after our last conversation ive split down the giant table into the smaller ones i posted in a reply on this thread, would you suggest as well that each of those listed tables they should have a "log" table for each "order weather log"  etc... 

[Joseph_Seddik]

Yes, if you need to keep the logs this is what you should do. Otherwise, you don't have to. 

[AGairAdmin]

and referencing another post i made about archiving changes such as edites and not "official" logs , would you think having 3 tables per , so a "primary table" ,"child log", and  "table edits log" 

[Joseph_Seddik]

Where is that post please?