The Edit in Grid mode, as we knew it from previous versions, no longer seems to be available. Is there any plan to bring this functionality back?
We would very much like to see it return, allowing end users to enable Edit in Grid for specific datasets. The ability to navigate from record to record and modify field values directly within the grid, without having to repeatedly click Save and Edit for each change, was very powerful.
This functionality is also missed in the Software Factory, where it provided a much more efficient editing experience.
Could you share whether this feature is on the roadmap?
Best answer by Erik Brink
Hi Harm and Mark,
The Universal GUI works fundamentally different in this in compare to the formal clients. Before a single component was editing. Now the entire subject is editing, as long as it is allowed by the settings, of course.
As mentioned before, if you only enable auto-save without auto-edit, you get the experience like we were used to before. The user enters edit-mode manually and can keep editing multiple records till he/she manually saves/cancels through the actionbar. So the manual actions are now the new triggers to start and to end.
For the issue Peter mentioned, this is fixed in recent versions. Currently, the SF offers auto-save checkboxes for both the grid and the form. Before the component had to be visible on the screen to get the setting enabled. This is recently fixed. Best is to enable auto-save for both or for the component that is initially visible on the screen. In recent STS versions, it does not matter whether it was visible already. This will officially be released with the 2026.3 platform release.
If you feel like the triggers of this are not clear enough, we can open up an Idea for that to post suggestions. Know, in the time this was a well thought decision of our designers to offer it like it is now.
It is working like that if ‘auto save’ is enabled. This is not done on all subjects in the SF unfortunately.
There only seems to be a bug currently that if you are using a screentype with a form you will first need to open the form one time before it starts working. I have reported this in TCP.
Has the usage of the ‘auto save’ setting fixed the issues that you were experiencing?
If you are missing this in some places in the software factory, could you open an idea with the specific places where you would like to see this change?
I believe the behavior we previously had with “Edit in Grid” was more ideal and should be restored and enabled for all grids in the Software Factory.
A small safeguard to prevent accidental changes is good. However, once a user explicitly chooses to edit in a grid, the interface must allow smooth navigation between rows using arrow keys or the mouse, and enable direct data editing without forcing the user to save every single record individually. Restoring this workflow would significantly improve productivity for us as developer but also for the users of the applications that we deliver.
I also would like the option for “Edit in grid” to return, so a user can enable it when he/she has need for it. Not specifically talking about the SF, but also a s feature I’d like to make available in our application. Having grids default editable is quite a risk as some users misclick/-type while navigating and think they just need to put that field back to the original state is enough, but they forget that possible defaults have affected more and they save the new state.
The Universal GUI works fundamentally different in this in compare to the formal clients. Before a single component was editing. Now the entire subject is editing, as long as it is allowed by the settings, of course.
As mentioned before, if you only enable auto-save without auto-edit, you get the experience like we were used to before. The user enters edit-mode manually and can keep editing multiple records till he/she manually saves/cancels through the actionbar. So the manual actions are now the new triggers to start and to end.
For the issue Peter mentioned, this is fixed in recent versions. Currently, the SF offers auto-save checkboxes for both the grid and the form. Before the component had to be visible on the screen to get the setting enabled. This is recently fixed. Best is to enable auto-save for both or for the component that is initially visible on the screen. In recent STS versions, it does not matter whether it was visible already. This will officially be released with the 2026.3 platform release.
If you feel like the triggers of this are not clear enough, we can open up an Idea for that to post suggestions. Know, in the time this was a well thought decision of our designers to offer it like it is now.
