I have ColumnA with 3 values. When “Value1” is selected then ColumnB is shown and requires user input.
I have set the “Reset on edit” property on Column B and insert an Initial Value of:
IF([ColumnA] = "Value1",
[_THIS],
""
)
The intent is to reset ColumnB if ColumnA is changed to a value other than “Value1”.
When editing, the first time ColumnA is switched from “Value1” to something else, ColumnB is reset as expected.
But while in the same editing session if I again set ColumnA to “Value1”, choose a value in ColumnB then switch ColumnA once again to a value other than “Value1” - ColumnB is NOT reset again. See image
I have tried removing the Show_If expression and using a targeted "Reset on edit: expression shown above as well as just setting the “Reset ion edit” w/o an expression
…I get the same behavior.
The issue is if a user does this activity, it leaves an unexpected value in the field that could impact downstream processing. Yes, I could implement an action on save but then I’d need to every time this is potentially possible - my particular app has several of these.
The bright side is the users are not going to flip back and forth very often at all but still…!!!
And I don’t seem to recall this being a problem in the past…so maybe it’s a new issue???
Anyone else experienced this problem and figured out a work around in the column configurations?
It happens to me often, but what I finally understood (perhaps the hard way) is that Reset on edit refers to when the row is updated—in other words, it recognizes changes when an existing record is edited.
The Initial value is just an initial value, but if it is changed, it cannot revert back unless you close the form and reopen it—it loses its initial value condition.
As a workaround, you could use the Valid If condition on the next field so that, if it is a dependent list based on the previous field, the values will be automatically cleared if the previous field changes.
In other words, instead of using Suggested values, use Valid If.
1 Like
Yes!!! I wasn’t thinking. To para-phrase…once a user physically changes that value in ColumnB, the Initial Value will no longer get applied - even with a “Reset on edit”!!
I’ll just have to live with it!
1 Like
Honestly, I understand you, especially because of your vast experience and how you help us in this community every day. It must be really frustrating (just like it is for me) to see how, on some occasions, such a great resource as the Feature Ideas section is wasted instead of being used to expand this platform.
A big hug, my friend.
Hi! It’s been a year since this post, but I’d like to revisit this topic. Did you manage to find any alternatives? I’m experiencing the exact same problem 
.
Could you elaborate on your use case? There is likely a work around but it may depend on your precise needs as to what works best.
One way I have come to think about this scenario, once a user changes a value, they have “control” over that field until they tap Save.
Here are some things that might be helpful:
-
Prevent editing of the field BEFORE they have a chance to change it. If certain conditions make it so you do not want the user to change the value, then you can insert an expression to control when the field can be edited by the user and when it cannot.
-
If the users inserts a value that does not align with the rest of values, you can use Validation to inform the user the value they chose is invalid .
-
If you want to “silently” update a value, you can do so AFTER they tap Save by attaching an action (or set of actions) to the Form Saved Behavior
If you have any additional questions, please ask
I hope this helps!!
