Solved: Allow user input in spite of app formula?

JMacFeegle

My app manages a bunch of OpenEPaperLink tags.

Usually, the values displayed on these tags comes from one parent table, so I'm selecting the row I want displayed and all fields are filled in via an app formula.

BUT sometimes it's necessary to change some or all of that information for single tags manually for [reasons].

Is there a method/workaround to allow user input on fields that are normally populated by an app formula?

JMacFeegle

OK, so it seems I found a solution, maybe it's helpful for others:

Give the columns in question an initial value that references the parent record, NOT an app formula. Problem: If this is set to reset on edit, so it refreshes when a new record is picked, every time something is changed it will reset the whole thing. Not ideal. Thus:

Create an additional (physical) column with a Change Timestamp for edits on the field that selects the record.

Set the columns to reset on edit, IF timestamp=now()

This will allow the user to edit the field(s) populated by the initial value. Further edits will NOT reset the whole thing. ONLY if the referenced record changes (another record is picked) will all fields reset to their initial value, now related to the newly picked record. Which could then be changed again.

View solution in original post

JMacFeegle

I mean I _could_ just make a copy if this tag to another table, edit it, and have this data sent out as a new json file to replace the old one. BUT then the current content of the tag would not be reflected in the original tag table.

I guess I could automate just copying the new information back into the tag table with a Google script, but I'd like this to be handled by the app as much as possible.

Sqidward35

I’m not sure if you can mess with the system generated forms. But The best option is to generate a new google forms or data sheet and connect it to database. Then connect it as a view, allowing users to edit and input form Fields. if database is set to private then the fields will only display for allowed users.

JMacFeegle

OK, so it seems I found a solution, maybe it's helpful for others:

Give the columns in question an initial value that references the parent record, NOT an app formula. Problem: If this is set to reset on edit, so it refreshes when a new record is picked, every time something is changed it will reset the whole thing. Not ideal. Thus:

Create an additional (physical) column with a Change Timestamp for edits on the field that selects the record.

Set the columns to reset on edit, IF timestamp=now()

This will allow the user to edit the field(s) populated by the initial value. Further edits will NOT reset the whole thing. ONLY if the referenced record changes (another record is picked) will all fields reset to their initial value, now related to the newly picked record. Which could then be changed again.

JMacFeegle

I was inspired by this post by @1minManager :

https://www.googlecloudcommunity.com/gc/Tips-Tricks/quot-Reset-on-Edit-quot-when-anything-in-a-speci...