Solved: Allow user input in spite of app formula? - Page 2

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