Auto-save is currently being triggered after another action including switching to another record. Only moving focus away will not save the record indeed.

Not being able to switch records sounds like a bug. Wild guess: do you have model insides enabled? If so, it will be a known issue.

Hi Erik, 

Thanks for the answer, is the auto-save going to change? Because I think moving focus should actually save the record. :)

Model insights was not turned on I believe.

No, I don't think this is going to change in the near future. The Universal GUI has a less focus-based setup in compare to the Windows interface. Leaving the edited subject now shows a message to save stuff. I think the auto-save mechanism should try to save in these cases too. So it will be saved whatever the user is going to do next.

“When entering the screen, I cannot change records because of the form being in edit mode, we first have to cancel the row and select a new row.”
Sounds like the GUI didn't have the auto-save mechanism enabled for some reason.

Hi ​@Erik Brink , 

For a customer I have form in auto-edit/auto-save, but this doesn't work if I understand correctly. I will always have to hit the save button? It's a single form for a single record. How can I auto trigger a save?

Hi ​@Freddy,

In this case auto-save will be triggered when the subject is left or when any other action is triggered, like executing a task.

For the case Robbert described in the past you can now easily use the auto-commit logic on a particular field. In you example this might save the record after every field being edited.