This question is locked. New answers and comments are not allowed.
Is there any way to prevent the user from doing the 3-sort click that removes any sorting on that column? We are using a domain data source to load the data and came across the issue where if you do the 3-click sort on a column, on the 3rd click the sort descriptor is removed. The problem with this is if you have paging enabled and specified a load size, when the DDS attempts to load the next set of records, you get the following error:
"The method 'Skip' is only supported for sorted input in LINQ to Entities. The method 'OrderBy' must be called before the method 'Skip'."
One solution we know is simply to perform an order by on every single "get" RIA service method but we shouldn't have to if we've applied the sort to begin with.
Is there no way to ensure if there is a sort applied we ensure the user cannot remove it?
"The method 'Skip' is only supported for sorted input in LINQ to Entities. The method 'OrderBy' must be called before the method 'Skip'."
One solution we know is simply to perform an order by on every single "get" RIA service method but we shouldn't have to if we've applied the sort to begin with.
Is there no way to ensure if there is a sort applied we ensure the user cannot remove it?