Wow, turns out getting the date filtering portion to handle a wide range of conditions with and without timezones was very tricky. Thanks for your patience. This feature should be available in the next nightly build, and eventually in the 8.1.23 release.
Some things worth mentioning. We do our best to determine the filter type of the column when the render mode is set to "auto". This is easy to do when the data is a dataset type, but a little trickier when it is an array of JSON objects. In this case, you may want to specify the render mode. If render mode is set to "view", we use the same method to detect the filter type, as if it were "auto" .
We've included four filter types, number, date, boolean, and string. Each filter type has a condition and, all but the boolean type, a value. For the date and number column filter types, that value can either be a single date or number, or an object representing a range (min and max). Just something to keep in mind when binding to the value of these column filter types.
Individual column filters are applied after the main text filter, if it happens to be configured and not empty.
Individual column filters can be hidden from the end user, so that you can just run them behind the scenes.
I think that's the bulk of what you need to know. We do have plans to add more conditions and filter types. If you have something in mind, feel free to let us know and we'll see if we can add it to the list. I'll leave you all with a few screenshots of the UI and some of the property structure. Not all of it though, wouldn't want to spoil it.
