Start Index for aggregates inside Data Actions in Reactive
410
Views
10
Comments
New
Aggregates & Queries

Recently, a requirement forced me to use a Data action to fetch data from an external database. 

In Reactive, this means the Start Index is not available as a parameter, which means implementing pagination requires 10 times more work than a regular aggregate.

The problem and solution are clearly explained in this forum post.


It feels like there should be a more immediate way to do this, since OutSystems is pushing Reactive Web as the future, and integration with external databases as one of its main selling points.


Thank you


asdqwerty.png

I agree with you, it would be much more simple !

Regards



Good Idea ,should be much Feasible for the developers further 

Other workarounds is Advanced SQL:

https://www.outsystems.com/forums/discussion/56822/reactive-web-application-paginate-a-table-with-an-advancedsql-source/


A bit out of left field for what should be out of the box features

Similar to: https://www.outsystems.com/ideas/2827/aggregates-starting-at-index-x-aggregates-paging/

Thanks André!

Yes, similar, but not quite the same. In fact, there's a comment there about there being Start indexes now in Aggregates for Reactive, and this is an issue happening in reactive, where Start index is not available if the aggregate is within a "Fetch data from other sources" type of call. 

I agree with you! Having the same problem, would love to have this changed.

No, it's not. This is specific to Reactive. That idea was posted in 2017 before Reactive even existed. 

2026-02-26 06-29-24
Rahul
 
MVP

Voted.
It should be to avoid use SQL only for pagination inside server action.

I agree that this would be very helpful and prevent us from needing SQL for simple pagination. I just wanted to add that it would be great not only in Data Fetch actions but in any server action.