Christopher
Top achievements
Rank 1
Rank 1
Christopher
asked on 12 Mar 2015, 05:24 PM
Hi,
I've been evaluating the Kendo UI Grid for some reporting requirements we have in some of our core products. We are primarily looking at the grid to save us time implementing our own.
I have been having a couple of problems and I wanted to find out if these were limitations of the grid or just problems with the way I am implementing it.
We need the grid to be able to display a large number of rows (over a hundred thousand). The grid seems to handle this very well in both paged mode and when using virtual scrolling.
The problems I am having start when using grouping in combination with volume data. The groups themselves are displayed fine, but when collapsing the first group in the grid in either paged or virtual scroll modes, only the one collapsed group is displayed at the top of the grid. I would expect the grouping to either re-paginate a paged view, to bring the next group into view or collapse groups in virtual scroll mode.
The expanded / collapsed states of these groups also seems to be lost when scrolling / paging through the grid after it reads more data from the server.
Another related issue is that row selection state also gets lost when the grid reads from the server, which means that you can't multi-select rows over page / scroll boundaries.
I have been using the Ajax bindings primarily, hooked up to an IQueryable using the ToDataSourceResult method and returning the data in Json format.
I have tried with database connections using EF and also with a set of auto-generated test data.
I would appreciate it very much if you could confirm if these are known limitations so that I can estimate how much work would be involved in working around them from our own code.
Many thanks,
Christopher Priest.
I've been evaluating the Kendo UI Grid for some reporting requirements we have in some of our core products. We are primarily looking at the grid to save us time implementing our own.
I have been having a couple of problems and I wanted to find out if these were limitations of the grid or just problems with the way I am implementing it.
We need the grid to be able to display a large number of rows (over a hundred thousand). The grid seems to handle this very well in both paged mode and when using virtual scrolling.
The problems I am having start when using grouping in combination with volume data. The groups themselves are displayed fine, but when collapsing the first group in the grid in either paged or virtual scroll modes, only the one collapsed group is displayed at the top of the grid. I would expect the grouping to either re-paginate a paged view, to bring the next group into view or collapse groups in virtual scroll mode.
The expanded / collapsed states of these groups also seems to be lost when scrolling / paging through the grid after it reads more data from the server.
Another related issue is that row selection state also gets lost when the grid reads from the server, which means that you can't multi-select rows over page / scroll boundaries.
I have been using the Ajax bindings primarily, hooked up to an IQueryable using the ToDataSourceResult method and returning the data in Json format.
I have tried with database connections using EF and also with a set of auto-generated test data.
I would appreciate it very much if you could confirm if these are known limitations so that I can estimate how much work would be involved in working around them from our own code.
Many thanks,
Christopher Priest.