Hello,
I'm using a kendo grid with scrollable: { virtual: true } with a kendo datasource with serverPaging.
This works fine when the grid is only used to read data, but i'm experiencing strange effects with CRUD operations on the datasource.
Especially when a datasource.cancelChanges() is called when the grid is on another page then the first page.
When I edit any of the model fields and decide to cancel the changes this is what happens:
- the Model.set has been called due to leaving the input (blur event)
- dataSource.cancelChanges will be called.
- dataSource jumps to first page.
Side effects:
- page data is out of sync and doesn't show the first row anymore.
It even gets weirder when I use dataSource.cancelChanges(myModel) when i'm on another page then the first page.
The entire row disappears from the grid which leaves the grid showing 14 rows instead of 15 (pageSize).
All in all the whole paging mechanism appears to be extremely buggy in a real world application (including CRUD operations.. etc)
I'm using a kendo grid with scrollable: { virtual: true } with a kendo datasource with serverPaging.
This works fine when the grid is only used to read data, but i'm experiencing strange effects with CRUD operations on the datasource.
Especially when a datasource.cancelChanges() is called when the grid is on another page then the first page.
When I edit any of the model fields and decide to cancel the changes this is what happens:
- the Model.set has been called due to leaving the input (blur event)
- dataSource.cancelChanges will be called.
- dataSource jumps to first page.
Side effects:
- page data is out of sync and doesn't show the first row anymore.
It even gets weirder when I use dataSource.cancelChanges(myModel) when i'm on another page then the first page.
The entire row disappears from the grid which leaves the grid showing 14 rows instead of 15 (pageSize).
All in all the whole paging mechanism appears to be extremely buggy in a real world application (including CRUD operations.. etc)