Interesting. I see that your issue right away. Two options I can think: 1. Manual solution: click “load more” until the option is no longer available. 2. Use javascript to detect when more records can be loaded and do so. Your issue will then be that the page can sometimes crash with the number of records being returned. You could test to see how many records you need to pull into the model to see when it crashes, but this isn’t an ideal way to set the upper limit. I wonder if there is way to dynamically pull in as many records as capable and display a message when there are more records that can’t be displayed. I wonder what Skuid has been contemplating on how to handle this.

Hi,

A few observations:

You definitively want to minimize the number of records pulled into the client.

Use search/filters to reduce the query set.  Are you using Server or Client side searching?

Instruct your users to leverage the Load More option per Pat’s suggestion. 

Have you explored Aggregate models?

Regards,
Irvin

We definitely reccomend using aggregate models to show visualizations for large datasets.  Its much better to have the server crunch the numbers and send a very thin dataset across the wire.  

Unfortunately - this will make it difficult if you want to show details and have the visualization update in real time as the details are searched and filtered.  We are working on ways around this issue. I’ll try to post some ideas later. 

Is Load More Option is Out of the box of SKUID? To what extent it can load ?