Why isn't supportsPaginationOnAggregatedQueries available for feature non-hosted feature service?
Solved! Go to Solution.
I had a friend putting a inquire request to ESRI and this is the response
We have one instance of this inquiry having had happened with Esri Inc many years ago.
The developers and product managers noted that pagination is not supported with outStatistics or returnDistinctValues on feature layers. The thoughts are that when making this kind of query, with its specificity, it should not need to return 1000s of records, requiring pagination - that number of records would not return any meaningful information. outStatistics and returnDisctingValues are meant to be used only on a handful of records, not 1000s.
We don't have any specific recommendation for you to suggest avenues to work around this design.
What would likely need to happen is that the data would need to be manipulated at the database level, through specific SQL queries or data manipulation, prior to it being published as a service. In this way, the query either would not require distinct values, or would not require pagination.
I guess we won't get a function anytime soon
I had a friend putting a inquire request to ESRI and this is the response
We have one instance of this inquiry having had happened with Esri Inc many years ago.
The developers and product managers noted that pagination is not supported with outStatistics or returnDistinctValues on feature layers. The thoughts are that when making this kind of query, with its specificity, it should not need to return 1000s of records, requiring pagination - that number of records would not return any meaningful information. outStatistics and returnDisctingValues are meant to be used only on a handful of records, not 1000s.
We don't have any specific recommendation for you to suggest avenues to work around this design.
What would likely need to happen is that the data would need to be manipulated at the database level, through specific SQL queries or data manipulation, prior to it being published as a service. In this way, the query either would not require distinct values, or would not require pagination.
I guess we won't get a function anytime soon