This question is locked. New answers and comments are not allowed.
We are using the MVC Grid - Q1 2011_1_315 release.
The grid is databound using the Ajax custom binding, since we have our own paging logic. (We use EF 4.1 Code First for data access)
Selecting data is functioning normally and the correct parameters are received via the GridCommand structure. (Page size - Page offset - SortDescriptors)
When performing a delete, insert or update operation, we receive an incorrect GridCommand structure. When the grid is sorted on one column (which is a requirement to use 'skip/take' in EF) , we receive incorrect sort description values. The SortDescriptors collection of the GridCommand structure contains one sort descriptor with only the SortDirection specified - the Member value is null.
As a consequence the subsequent fetching of the data fails due to the missing sorting information.
Is this a known issue?
The grid is databound using the Ajax custom binding, since we have our own paging logic. (We use EF 4.1 Code First for data access)
Selecting data is functioning normally and the correct parameters are received via the GridCommand structure. (Page size - Page offset - SortDescriptors)
When performing a delete, insert or update operation, we receive an incorrect GridCommand structure. When the grid is sorted on one column (which is a requirement to use 'skip/take' in EF) , we receive incorrect sort description values. The SortDescriptors collection of the GridCommand structure contains one sort descriptor with only the SortDirection specified - the Member value is null.
As a consequence the subsequent fetching of the data fails due to the missing sorting information.
Is this a known issue?
1 Answer, 1 is accepted
0
David
Top achievements
Rank 1
Rank 1
answered on 12 May 2011, 10:12 AM
Hi Luc,
Try using the GridState object instead the GridCommand object when using AJAX BINDING.
Try using the GridState object instead the GridCommand object when using AJAX BINDING.