Unplanned
Last Updated: 25 Feb 2020 10:43 by ADMIN
Created by: Mat
Comments: 0
Category: Filter
Type: Feature Request
1

Hi,

I notice you have added support for specifying the format of expressionPreview fields, which is great when handling dates and numbers, so thanks for that.

However, ideally I need to be able to use a template for the expression preview for certain fields. For example, take the scenario where you are filtering for 'user_id'. Currently I'm using a custom editor to present a drop-down list of user names to pass the user_id to the filter, which works well, but the expression preview looks like:

User Equals '132'

rather than:

User Equals 'Fred Bloggs'

If I could use a template for the expression preview, I could use a function to display the name associated with the user_id.

This is just one example: there are many others where a template would be useful in the Filter Panel expression preview.

Unplanned
Last Updated: 11 Feb 2020 09:18 by ADMIN
Scheduled for 2020.R1.SP.next

When using the Filter control and configuring the Fields, if a 'number' type field is used, the value 0 (zero) is ignored, for example:


$("#filter").kendoFilter({
    dataSource: dataSource,
    expressionPreview: true,
    fields: [
      { name: "age", type:"number", defaultValue: 31 },
      {name: "foo", type: "number", defaultValue: 0},
      { name: "name", type:"string", defaultValue: "Rick" }
    ]
  });

'age' and 'foo' are both 'number' type fields, but the default value of 'foo' will be ignored when the filter is chosen in the UI.

 

Here is a runnable example of this, notice how when selecting 'age' from the fields dropdown, the value correctly defaults to 31, but selecting the 'foo' field will not have the value populate correctly:

https://dojo.telerik.com/eHAROSOz

Completed
Last Updated: 04 Dec 2019 15:00 by ADMIN
Release R1 2020
Created by: Mat
Comments: 0
Category: Filter
Type: Feature Request
2

There are occasions when the out-of-the-box filter operators can't be used, such as filtering on nested objects. In these situations I use a custom function for the filter operator.

It would be great if the Filter widget could support custom filter operators.

I realise this would be challenging, as it would break the save/load state function and would be difficult to handle in the expressionPreview.

Declined
Last Updated: 08 Oct 2019 10:03 by ADMIN

Reproduction of the problem

  1. Run the dojo at https://dojo.telerik.com/@GaloisGirl/uBiLIbiP/3 . The state of the filter is "(ContactTitle Is equal to 'Sales Representative')", however, the ContactTitle field has been commented out from the dataSource schema.

Current behavior

The error "TypeError: Cannot read property 'type' of undefined" is thrown

Expected/desired behavior

Some error should be thrown, but one that the developer can recognize and handle appropriately.

Your example of persisting state saves it in localStorage. Say my user saves the state on Monday, and by Tuesday, a column is removed, renamed, has a different type... I need to handle that user's deprecated saved state.


 

 

Completed
Last Updated: 13 Jan 2020 09:15 by ADMIN
Release R1 2020

Reproduction of the problem

  1. Open dojo at https://dojo.telerik.com/@GaloisGirl/AqotEtep
  2. Click "Add expression" and pick "Product name",  "Is not equal to", "".
  3. Click "Apply". The grid show 77 items, as expected.
  4. Click "Add group" and then "Apply".

Current behavior

The grid shows 0 items. The expression preview is (Product Name Is not equal to '').

Expected/desired behavior

The grid should show 77 items. For an optimal user experience, the empty groups should be deleted when applying the filter.

Completed
Last Updated: 04 Dec 2019 14:59 by ADMIN
Release R1 2020
Created by: Mat
Comments: 1
Category: Filter
Type: Feature Request
2

Hi Team,

When a date filter is applied in the new Filter widget, the preview looks like: "Date Is After 'Tue Jan 01 2019 00:00:00 GMT+0000 (Greenwich Mean Time)'" -- I'd like to be able to customize the displayed date format, something like adding "format:"{0:dd/MM/yyyy}" to the 'fields' object.

Thanks