Ordering on a complex type does not work. about datatables.queryable HOT 3 CLOSED

@VictorioBerra I think it should be separate setting in DataTablesColumn, like existing ColumnSearchPredicate.
I've already implemented this in commit. So the usage will be something like this:

Server-side:

// take column options
var column = request.Columns[p => p.ManagedBy];
// set search predicate
column.ColumnSearchPredicate= p => p.ManagedBy.Name.Contains(column.SearchValue);
// set ordering by nested property (Name)
column.ColumnOrderingProperty= p => p.ManagedBy.Name;

Client-side:

{
    targets: 3,
    "data": "ManagedBy",
    "render": function (data, type, row) {
        return row.ManagedBy.Name + ' (' + row.ManagedBy.EmailAddress + ')';
    }
},

from datatables.queryable.

So, in order to get around the error and specify a property you can do something like this in your table columnsDef:

{
    targets: 3,
    "data": "ManagedBy.Name",
    "render": function (data, type, row) {
        return row.ManagedBy.Name + ' (' + row.ManagedBy.EmailAddress + ')';
    }
},

But my server still evaluates this locally because of the complex object.

from datatables.queryable.

@AlexanderKrutov Is there a way we could do ColumnOrderingPredicate instead somehow? A more advanced situation is needing to do cusomers.OrderBy(x => x.CustomerOrderLine).OrderBy(x => Order.Name)

I have an issue now with needing to order by properties inside my many to many relationship. I wonder if this will get easier when EF Core lets you omit the many-to-many table? then the nestedt properties will exist without jumping through the associative table.

from datatables.queryable.