Hi @knepiosko,
From what I have seen in lobbies, it is true that “FETCH NEXT 100" is added to the query when you debug, and the main reason behind this is to avoid performance issues. Most of the lobby element types are designed to provide a high-level overview of the data, hence won’t show the full set of a huge data pile.
This limitation has been intentionally actioned as this will avoid the rendering issues in using lobbies.
As a suggestion, you can use list elements to display huge data sets.
Hope the above helps!
Cheers!
Novishan
Thank You Novishan Dissanayake
But I still do not know the value of :MAXROWS in non-debug activities.How can I identify whether all needed rows were fetched in Aurena?
What is the element type and data sourceyou have used? Where do you aggregate? at the data source or at the element?
This is standard bug and correction will be done in UPD13
Hi @gope
I do not know the number of bug. I suppose correction was done in Aurena Binary patch.
Ok, what about App10 IEE client it has the same sad behaviour I think
Hi @gope
IEE works well all the time.