My application has a ton of grids with a ton of columns so we've got a bunch of slick code to essentially generate most of the grid settings based upon schema objects. Yesterday I began working on the Excel-like multi-filtering. I was working with the Q1 and got it working nicely except for 2 things. Filtering "null" wasn't working at all, and filtering dates wasn't working. Today I sat down to fix those 2 problems and realized I had just barely missed the Q2 release. Wondering if these issues were fixed I find I can't even get far enough to find out.
I've got the following code which generates the multi-filter based upon a schema object representing a given field.
column.filterable = column.filterable || {};column.filterable.multi = true;column.filterable.dataSource = { type: "aspnetmvc-ajax", transport: { read: { url: excelFilterUrlBase + "/"+ field.charAt(0).toUpperCase() + field.slice(1), // Evaluates to something like 'api/Employees/LastName' data: primaryDataSource.transport.read.data, type: "GET", dataType: "json" } }, schema: { data: "data", total: "total", model: (function(fieldName, field) { varmodelObject = { id: fieldName, fields: {} }; modelObject.fields[fieldName] = { type: field.type } returnmodelObject; })(field, fields[field]) // Evaluates to a proper model object having the correct 'type' }, filter: primaryDataSource.filter}
When I run this code and then click on the column menu dropdown, I see in the network traffic that it properly calls my service method, and gets back the appropriate JSON response object:
{data: [{lastName: "Aaron"},{lastName: "Abbas"},{lastName: "Abbott"},{lastName: "Adams"},{lastName: "Adhikari"},{lastName: "Agarwal"},{lastName: "Aggarwal"},{lastName: "Aguilar Schall"},//...],total: 908,aggregateResults: null,errors: null}
However, In my grid, I only see the "Select All" checkbox. There aren't any other options.
This was working in Q1. What changed?