In the universal, there is pagination (e.g. 100 rows). How can a user perform a task for all the rows in the table, instead of only the 100 that is currently shown?
In the universal, there is pagination (e.g. 100 rows). How can a user perform a task for all the rows in the table, instead of only the 100 that is currently shown?
Hi Martijn,
We have a User story for this on the backlog! This will then allow you to run tasks for the selected row(s), all rows on the current page or a complete dataset.
Currently, a task could potentially affect the whole dataset if the underlying stored procedure affects the whole dataset. However, a task that runs on selected records cannot run for the entire dataset at the moment, only for the selected records on the page.
Hi Mark,
Thanks for your response. Glad that you have it on the backlog. Is there an expected release date?
We sometimes have 6000+ rows in a table, so that might give some issues if it needs to be done per page.
Hey Martijn,
Looks to be that we are aiming to deliver this with 2025.3 😄
I don't see it in the current release candidate. Does that mean that it won't be in 2025.3?
We do expect to finish it before end of the year.
Oh, that sounds like bad news. We have some people waiting for this before they can switch from windows GUI to universal GUI. I already mentioned the “aiming for 2025.3” which will release on Monday, so I think they will be disappointed with the 3 months delay.
Is there a way to keep track of these planned/aimed features and already see in advance if the proposed deadline is going to be met or not?
This particular Feature is tracked in below Idea by the way:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.