We have a WebDataGrid which we would bind the entire datasource to. However, this turned troublesome as the datasources got larger and now we are experiencing some timeout problems. It also seemed very unneccessary to fetch the entire dataset from the database when only one page can be displayed at a time anyway. The way out seemed to be to use custom data binding and only bind a subset of the datasource, enough to fill the current page displayed. But this resulted in problems when trying to sort or filter on the records in the grid since both of these actions by default are performed on the datasource (which only consists of a few items).

One possibility would be to catch onSort and onFilter events and write a custom implementation of this functionality. However, these changes would mean adding more SP:s to handle the events and this will probably present us with additional maintenance work in the future.

My questions are:

 - Is there any other way of speeding up performance in Infragistics WebDataGrid when working with large datasets, without having to write custom data binding, custom filtering and custom sorting?

 - I'm also curious as to how to make the WebExcelExporter work when using custom data binding. The option DataExportMode.AllDataInSource will still only export the subset data source. Currently we have to re-bind the grid with the full datasource (and hope that it does not timeout) before performing the export. Is there a way around this?