Alright, so 2 brains were better than one for this sneaky issue.
If it can help anyone else: having the “show thousand separator” option checked was preventing the reset process to work properly. It works fine if, instead, the “formatted as 1,029” is used to format directly the input value, and the option “show thousand separator” is left unchecked.
Tried that already @anon65040322 - but even so that’s not the point… it would be far better to be able to select the ‘relevant’ inputs or inputs by id - as opposed to relying on bubble’s algorithm to do so. Relying on the group hack is just that - a hack used only when reset relevant inputs doesn’t work as intended.
As described in the thread there are edge cases where the reset inputs clearly do not work as intended. Snide replies to genuine issues and possible bugs are counterproductive, and will likely increase the time it takes for the community to identify and fix errors.
This example show’s how a focused input doesnt reset when you press enter, only when you click out of the input.
The Reset event is called on every change, I also tried to shift the focus to a different input before
So, as you can see, when you press enter on an Input, the corresponding onchange event is executing (focus is shifted), but the focused input doesnt change.
I had this exact problem and finally managed to solve it.
If you want to target a specific input where “reset relevant input” doesn’t do the trick. All you got to do is in the workflow reference that group and then afterward add this workflow action.
Group the input > reset this group > reset relevant input
That’s why I created a super-easy plugin that could help you resetting a specific Input via its HTML ID.
You can check it here : Reset Data of an Input Plugin | Bubble