Alternative to grid with more than 10000 of data

Hi Varun -
It's not likely that any human could digest that much data at a glance or even a long review.

What's in the data the people need to know?

Hi Varun -
It's not likely that any human could digest that much data at a glance or even a long review.

What's in the data the people need to know?

@Rob Thanks for replying.
It's all about the different customers information shown in a grid format to the agent. Any possible way to do this.

Depending on the source of the data, query latency is a consideration in your use case: How long is it going to take to for appian to retrieve this data? Is it coming from database? If so, is this a table or a view? Are the indexes good?
What about if the data is retrieved from an integration. How long does it take to transmit the data over a web service? Does the service employ batch size and paging conventions?

If you're planning a database query, you might want to use an explicit user initiated search before running the query.
Also, you can include filter criteria to limit the result set down to something useful. (Again, no one is going to read 10,000 rows of data in a brief instant.)
These docs show how to create a filtered query.
docs.appian.com/.../Query_Recipes.html

Similar to the pagingInfo convention used in Appian queries. You can use paging info in your grid configuration to control how many rows to display to a user at once:
docs.appian.com/.../Paging_Grid_Component.html

Is this helpful?

Yes, Thanks Rob...