This is my first time posting in this community, and I’m a very novice Glide user (3 or so months in).
I’m building an attendance app for my school. I need to log a date choice, attendance taker name, event attendance is taken in, and the names of all the students who may be absent for the event.
I then need to send those individual student names into another table, creating new rows for each name indicated as absent. The row also needs to contain all the other information logged for the event (date, taker name, event, etc.).
In my existing form, I’m using a choice option and allowing for multiple selections. This creates an array of names along with the event information in a table.
What would your suggestions be to parse the array and create individual new rows associated with each name and include the event information in a new table?
Thanks @GrumpyRick! Unfortunately, my institution is not so interested in upgrading to the business plan… which I think is the only way to use the Glide API… Blarg.
The whole app is being used for attendance purposes and also to track what we call dings, which are like points that a student accumulates for various reasons in various spaces.
So in one part of the app, a user logs dings one by one for individual students. The cumulative data (ex. How many total dings a student has and the details for each individual ding) is then displayed in a few different ways depending on user roles.
For this attendance portion, I am looking to input absences (which also count as dings) but for many students at once (could be up to 75). Ideally, I would want to have a user be able to rapidly submit individual student absences in a single table, creating individual rows within that table with each submission. This would, ideally, be the same table as the rest of the dings being logged.
So to answer your question: It doesn’t have to be info duplicated in another table.
I still haven’t played with webhook options suggested by ThinhDinh, and am open to other suggestions!
It would be interesting to know what tables you have in your database (data editor) with what basic columns.
It would also be interesting to see some sort of diagram of your data, such as an entity-relationship diagram, to get an idea how the tables relate.
Starting with a solid database architecture makes building easier. And starting with an unsound database architecture makes building much more difficult.
I ask because there is no point parsing arrays and copying data from one table to another if the architecture of your database doesn’t play in your favor.
