I have a table where each row represents a customizable entry that users can personalize by selecting data from other tables.
What I’m trying to do is allow users to reset all these rows (clear their data) when they click a “Cancel” button — so that the next time they access the form, all fields are empty again and ready to be filled in.
The key requirement is: I want this reset to happen without consuming updates or using on-submit triggers.
I’ve seen a few topics around this, but haven’t found a clean way to achieve it yet.
Has anyone found a workaround or method for resetting multiple rows “virtually” or using computed columns? Any ideas or best practices are welcome!
First of all — thanks to the community for the many ideas shared on this topic. I did try the [template solution] previously suggested for resetting user-specific values, but it didn’t quite match what I needed for my use case.
So I’d like to share the solution I ended up using, in case it helps others in a similar situation.
I have a table where each user edits multiple rows, with user-specific columns like Ingredient and Percentage.
What I wanted:
When the user taps “Cancel”, or
When they simply reopen the form later,
All the user-specific fields across those rows should appear empty again.
Instead of erasing user data, I just hide it unless it belongs to the current session.
In the Users table
Session ID → text
A new value is generated when the user enters the form (I use Now() formatted as text).
In the Rows table (e.g., Ingredients):
Row Session ID → user-specific text
Stores the session ID when the row is updated.
Ingredient Visible → If-Then-Else
If Row Session ID = Users > Session ID → Then Ingredient Else → empty
Percentage Visible → same logic
When the user enters the form, a custom action sets a new Session ID in the Users table.
Each row checks if its Row Session ID matches the current session:
If yes → show the stored value.
If not → show blank (looks like a reset).
When the user saves or edits a row, a custom action writes the current Session ID into that row’s Row Session ID.
The form always starts clean, regardless of what was typed before
No data is truly erased — it’s just ignored if outdated
Yes, at its core, the logic is the same as the Parent ID approach, comparing a stored value per row against a reference value. But honestly, I didn’t fully understand how to apply it until I tried using a Session ID based on Now() to trigger the reset automatically when entering the screen.
That gave me exactly what I needed: no manual reset, user-specific control, and no updates consumed.
I want this reset to happen without consuming updates or using on-submit triggers.