Yes, that is the behaviour I’m seeing.
So far I’ve got it partially working - with a Save button that runs a snippet. The code in the snippet gets all of the relevant INPUT fields, then actions each one like this:
elems[i].dispatchEvent(new Event(‘onchange’));
that runs OK, but then when I add a following action on that button to Save the model, it still only saves any fields I have physically altered - BUT - strange this is if I then click the Save button a second time, it does recognise the changes and updates the record as expected.
Is it something to do with the onchange events firing but not completing before the Save is attempted?
