At present musoni use the runreports API heavily to fetch client, loan and savings information in the way they wish. For instance they use it in cobmo with the 'datatables' ui plugin to show all clients and allow filter across multiple columns on that data.
At first they fetched all client data using the runreports API and let datatables plugin handlethe paging and rendering of the data - this works great for datasets up to say 10k - but as datasets get bigger the amont of data coming back over the wire slows everything down (they are using the non-optimised return format 'genericResultset=false', a faster approach is to let the tablular data come back in default way which optimises JSON returned suitable for tables/datatables UI plugin).
What is request is the ability to optionally indicate that they would like the data returned in a paginated way. e.g. paged=true With this ability they would be able to reduce the amount of data coming back over the wire and still know all the details they need to provide to datatables UI like total records etc.
Important: The default behaviour of the runreports api should not be changed/affected by this. This is just a nice to have in cases where people use the runreports API with bigger datasets for workflow/search purposes.
@markus, Is this still an active feature request?
This is still something we would like to see, but more of a nice-to-have than a must have. In general it would be good to support here as well to keep it consistent with the other endpoints of the API.