Skip to main content
Question

New row selected after saving by using the + button

  • June 3, 2026
  • 2 replies
  • 17 views
D
Rookie
Forum|alt.badge.img

Hi all,

I'm not sure whether this is a new idea, but I haven't found any related community posts yet.

I have a client using UGUI (2025.3) for order entry. A significant amount of their order entry is done in succession using the + button. Users create a row, then click + again to add the next row rather than clicking Save between entries.

 

The challenge is that users still want to see the newly created row immediately after adding it. Currently, the grid only selects and scrolls to the new row after a Save action, not when a new row is created using +. As a result, newly added rows at the bottom of the grid may not be visible until their final save.

From the users' perspective, this slows down the order entry process because they cannot quickly verify that each line was added successfully before moving on to the next one.

 

I imagine there are other scenarios where users repeatedly use the + button without saving between entries, so this behavior may not be unique to this client.

Would it make sense for the grid to automatically select and scroll to the newly created row whenever the + button is used, in the same way when the save button is used? Has anyone else encountered this workflow or found an alternative solution?

 

 

2 replies

Nigel Smit
Rookie
  • Nigel SmitRookie
  • Rookie
  • June 5, 2026

Hi Djoeke,

Have you added page sizes to the grid?

When you add a new row using the “+” button and then press “+” again, this can create a new page. In that case, the grid will automatically navigate to the new page.

If you set the page size so that all rows fit on the screen without scrolling, the user will always be able to see the newly added record.

Kind regards,

Nigel Smit

D
Rookie
Forum|alt.badge.img

Hi Nigel,

Thanks for your response.

I tried using a page size, but like you said, whether the newly added record is visible then depends on the available screen space. For example for my laptop screen you would apply a max page size of 14, which leaves a lot of white space on my monitor. However with a larger page size I would still need to scroll using my laptop.

This could be a workable solution for exactly one user, if you know their screen size. But does not seem to be a clean solution. 

 

In addition, I have tried a descending sorting of the row id. In this case the row id is hidden in the GUI, so this will work, because new rows are always added at the top. I'll need to check with them if this solution is acceptable.
However, I have experience with a client that does use ‘order row numbers’ in their order entry, and in that case it would not do to change those to descending order. 

Still an interesting issue I think, to get a clean solution :)
Any ideas are very welcome,
Djoeke 

 

Terms & ConditionsAccessibility statement