Deployment confirmation

One of the least mobile things in the deployment is the information about who gets what and where. We can't possibly send the information by carrying around a bulky laptop when we deliver computers, so I need a mobile interface that allows me to input data and submit it to a database which will keep the deployment updated.
Google sheets can be the right thing for this since it allows access outside the intranet. The only problem is getting the right order connected. That's not such a big issue of I can connect the information to a predefined link from my page to Google which fills the fields I have information for and gives me quick access to update the parts I don't have information for. Easy solution.

Update:
This worked great. Using importrange in a couple places to get the data from the submission through storage reports and back out to the customer turned this into a live solution in a matter of a few hours. Updates do take about five minutes to populate the tables throughout the whole system though.

Update 18-Aug:
One bug that was relatively easy to fix: when comparing the number of results returned by the query to the database, it would sometimes run an integer comparison against the strong value, which prevented any results from showing. Using intval fixed the issue.

The only other reported problem is that sometimes Google forms freezes and forces a restart to the process. Didn't happen to often though, so no action was taken there.

Feedback was also given that it should be possible to see the status of the computer being reported so we prevent multiple entries. That is under construction with spreadsheets API and hopefully will lead to further development in the use of spreadsheets for storage control.

Link a dynamic appointment in a dynamic email

This was quite a success. I just need to link a CSV file to the page so it creates the emails and allows me to push them out in batches.. keeping the record of which people have received what mails and when and what content the mail contained.. easy with an identification number for each row.

Random thoughts of the Find

Input comes from CSV files, so I need to be able to parse them correctly into the database. Dumping them in works for now, but it's not going to hold in the long run because I need to be able to use validation to make the database understand the data. I also need to be able to update the data that already exists from each dump... That seems like it might actually take a lot of time to code, but I'm going on the hunch that it will save hours of validating data in the future.

I suppose I could use the existing dump of multiple CSV files and just dummy the input from each one where the information from the file exists in another table.

Either way, I need to look into how to use the mysql function together with file uploads to release the need to log into the database to input the data.