I have a checkbox that hides the submit button when un-checked.
I don’t know how it got that way; I’ve tried building the form again from scratch, I’ve tried creating a new Boolean column and assigning it there… nothing will get it to behave!
There are two other Boolean items in this particular form, each with their own default values, and the default value of this particular checkbox is on - but that shouldn’t make a difference, right?
OH - and it only happens when 1 of three choices has been made in the form preceding it…
Why do you need a form button that submits another row related to that request? Shouldn’t that info be on the same line as the original request or am I missing something?
With Airtable, I needed to have a separate FORMS table for every table containing data whenever I wanted to pull information from the data table and then make changes to that table.
I’m smack in the middle of moving this app from Airtable to Glide sheets, and now I’m wondering if maybe I don’t have to do that the same way?
Got it. The form request can’t submit an empty form…so when it’s unchecked, there’s nothing to submit. I bet if you type in some notes, you’d be able to submit the form.
It marks it as either approved or declined, adds notes, the number of hours approved (if any), removes the “pending” checkmark, and adds the “processed” checkmark.
Yeah, I realized after your last question that I had been doing something that I learned in Airtable that isn’t necessary when using Glide’s tables - namely, I had the forms populating their own table, and then automating new rows and updates to those rows in the actual table I needed to use.
That insight combined with @Robert_Petitto 's brilliant time tracker template helped me re-build the entire thing from scratch, so now I have fewer tables to manage (and therefore rows), and the actions are much more straight-forward.
