My situation is fairly common for lab instruments. Data containing hundreds or thousands of rows gets automatically spit into a csv without any identifying information whatsoever.
The appsheet csv upload action in behaviors is great at scraping the data from each csv; however, I can't seem to figure out a way to have appsheet tag this data for me.
For a fake but practical example here is what an instrument might spit out into a csv:
| temperature (C) | time (s) |
| 15 | 1 |
| 20 | 2 |
| 25 | 3 |
I would like the result to be the following as I upload the csv:
| Experiment Name | Date | Experimenter | ID | Temperature (C) | Time (s) |
| Temp Test 1 | 24-03-2022 | John Doe | adsfsd | 15 | 1 |
| Temp Test 1 | 24-03-2022 | John Doe | ewrtre | 20 | 2 |
| Temp Test 1 | 24-03-2022 | John Doe | qwewv | 25 | 3 |
ID and Date are fairly easy using UNIQUEID() and TODAY(), but the Experiment Name and Experimenter not so much.
In a perfect world I could have something like this app, but I don't think this is in the scope of the upload csv capabilities given it is an action. I do know this data can be technically brute forced and manually added to each csv prior to uploading, but I want to make this as automated as possible so that each new user requires little to no training to use the app.
I am going to keep exploring options either with a grouped action, parent/child tables, or bots to see if I can make something work. As I do that, I hope that someone may have insights on how to accomplish this already and can comment on this post.
Thanks everyone!
LinkedIn
Twitter
