This question is locked. New answers and comments are not allowed.
We are using 2011.2.712 in one of our projects and discovered a bug with GridSortMode.MultipleColumn
We found that the first select ajax request has all the correct order by clause, however, in the wrong order.
expected: section asc, township asc, range asc, farmserialnumber asc, tractnumber asc
actual: farmserialnumber asc, tractnumber asc, section asc, township asc, range asc
After subsequent paging the grid begins to behave correctly.
Only the initial ajax load was incorrect.
Our work around was to rearrange the columns in the grid to match the sorting order.
Our grid columns were rearranged to :
*more columns* | section column | township column | range column | farmserialnumber column | tractnumber column
for all the paging to work 100% as expected with GridSortMode.MultipleColumn enabled.
I could not find this in the forum when we initially were troubleshooting this bug.
.Sortable(sorting => sorting.SortMode(GridSortMode.MultipleColumn) .OrderBy(sortOrder => sortOrder.Add(o => o.Section).Ascending()) .OrderBy(sortOrder => sortOrder.Add(o => o.Township).Ascending()) .OrderBy(sortOrder => sortOrder.Add(o => o.Range).Ascending()) .OrderBy(sortOrder => sortOrder.Add(o => o.FarmSerialNumber).Ascending()) .OrderBy(sortOrder => sortOrder.Add(o => o.TractNumber).Ascending()) )We found that the first select ajax request has all the correct order by clause, however, in the wrong order.
expected: section asc, township asc, range asc, farmserialnumber asc, tractnumber asc
actual: farmserialnumber asc, tractnumber asc, section asc, township asc, range asc
After subsequent paging the grid begins to behave correctly.
Only the initial ajax load was incorrect.
Our work around was to rearrange the columns in the grid to match the sorting order.
Our grid columns were rearranged to :
*more columns* | section column | township column | range column | farmserialnumber column | tractnumber column
for all the paging to work 100% as expected with GridSortMode.MultipleColumn enabled.
I could not find this in the forum when we initially were troubleshooting this bug.