Translate
- Content Manager Explorer are Core Service APIs to be extended to get paginated results.
- Change APIs to return smaller result sets as specified by the client.
- Need the capability to paginate results for the list to reduce the performance impact.
What I would like to learn more about is what does the community really need from the product? Do you require paged result sets, or is it only a workaround to reduce the data set so that a list can be more performant?
Regarding improving performance or adding paged results, which lists are we talking about exactly (thanks Mark Saunders for listing a few already)?
The following idea is pointing here: Provide users the ability to manage long lists in the CME using pagination.
