What a ridiculous response. I'm dumbfounded that Telerik implemented sorting on ForeignKeys like this. These kind of issues are showstoppers.

Shocked that this is not supported. As a workaround i use this:

    public static class DataSourceRequestExtensions
    {
        public static void ReplaceSortColumn(this DataSourceRequest instance, string from, string to)
        {
            instance.Sorts.Where(w => w.Member == from).ToList().ForEach(s => s.Member = to);
        }
    }

useage:

        public ActionResult Entity_Read([DataSourceRequest]DataSourceRequest request)
        {
            request.ReplaceSortColumn("idColumn", "entity.text");

@CrazyTalk - Are you also filtering the same column and passing the list to filter drop down?

Is this fixed or supported in the latest version of Kendo?

crazytalk, could you copy and paste the piece of code where you doing this please?
Thanks ¡¡¡¡¡¡

As a workaround in my MVC.Net code I pass the text field concatenated with the id separated by a hyphen (Text+"-"+Id) to the kendo control
which means sorting by the id gives the correct order because the id starts with the text and is unique because it end in the unique id. when I pass the data back to the MVC application I separate the ID using a substring for the last instance of hyphen which works fine if your id’s are numeric

Who in the world would want to sort Column displayed as Text by the Id? Just say it is not implemented :)

Any update on this issue?

Hello,

I would just like to check with you if this is the final decision taken by Telerik (not to support this feature)? We have Kendo subscription in my organization and I use Kendo UI (in one of the projects - business, data driven web application) in combination with several odata web services (already implemented and deployed to the internal network), so if there's no possibility of within-grid data sorting by foreign key column value, which seems to be a regular requirement in any enterprise application, it brings the usage of the whole Kendo UI library in combination with odata web services under the question mark.

Thanks in advance.

If it has only key, use the key on sorting, but if it has a value also, sort using value instead of key.

Did this get logged as a bug, and is there any status update on it?