This is a general question about how the xamDataGrid is to be used in an enterprise application.
We are building an application with a very thin client application, and all of its data is retrieved from a set of WCF services. Of the areas where we may use data grids, several have potentially millions of rows that would have to be returned from the service and displayed in the grid. Obviously this is not practical from a performance standpoint, so the grid/data source would need to virtualize its data and only retrieve a few "pages" of data at a time. However, this has ramifications on the grid's ability to filter and sort since it would not have access to the entirety of the data at any given time.
What recommendations do the developers or users of XamDataGrid have in this scenario?
Thanks for reading! Any feedback would be appreciated.
Hello,
Leaving the XamDataGrid aside, filtering and sorting of millions of records has to be performed on the system where the whole data is available. Since you will bind only a small set of data to the XamDataGrid, you cannot do this in the XamDataGrid.
You will probably have to make the WCF Service retrieve only the filtered data (or again small set of the filtered data). But again, the filtering will be performed on the system that has access to the full data.
Hope this helps.
I assumed that this would be the case. Our service does support filtering, but how do I make those calls from within the grid? Does XamDataGrid provide hooks so that I can translate what is in the Grid's filtering user interface into our service call? Are there any examples of how this would work?