1. Feedback
  2. ASP.NET Core
  3. 12596

Welcome to the ASP.NET Core feedback portal. We’re happy you’re here! If you have feedback on how to improve the ASP.NET Core, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

3
Votes

Better way to define default FilterBar behaviour in DataGrid

The current suggested solutions for setting the default operator:

https://www.syncfusion.com/kb/3369/how-to-change-the-default-comparison-operator-of-the-filter-bar

OR https://www.syncfusion.com/forums/140367/filter-operator-contains

are less than ideal, as they disable support for the "*" startswith wildcard - meaning that users no longer have the option to use startswith if they want to: typing "*searchString" will still run the "contains" operator.

Could it be possible to add a way to configure this that leaves the wildcard functionality intact, such as a concrete "defaultOperator" property?