This is a migrated thread and some comments may be shown as answers.

why do i have to set EnableLinqExpressions="false"?

5 Answers 302 Views
Grid
This is a migrated thread and some comments may be shown as answers.
rdochert
Top achievements
Rank 1
rdochert asked on 23 Mar 2010, 11:25 PM
my application has lots of grids. i find that the filters are case sensitive and do not work with the apostrophe character unless i set
EnableLinqExpressions="false"

in the grid definition. naturally, i dont want to have to do this for every grid in my application. i'm wondering why the default would be set to true when it has such an impact on existing functionality?
cheers,
rob

5 Answers, 1 is accepted

Sort by
0
Nikolay Rusev
Telerik team
answered on 24 Mar 2010, 11:01 AM
Hello Rob,

You can control whether the filter expressions that RadGrid builds are case sensitive or not by setting CaseSensitive property.
http://www.telerik.com/help/aspnet-ajax/telerik.web.ui-telerik.web.ui.gridgroupingsettings-casesensitive.html

Regards,
Nikolay
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
rdochert
Top achievements
Rank 1
answered on 24 Mar 2010, 11:39 AM
but how do i avoid having to set that on every single grid in my application?
0
Nikolay Rusev
Telerik team
answered on 25 Mar 2010, 10:39 AM
Hello Rob,

I am afraid that you will have to set the property on every grid. Just like any other property of RadGrid.

Kind regards,
Nikolay
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
rdochert
Top achievements
Rank 1
answered on 25 Mar 2010, 10:49 AM
"Just like any other property of RadGrid."

sorry - but that is not correct. the overwhelming majority of properties have sensible default values, otherwise every aspx page with a grid on it would be ten pages long.

in the past, the filters on radgrid ALWAYS worked CASE INSENSITIVE. in my opinion, this should be the obvious choice for the default because most people performing searches do not want them to be case sensitive. 

So my point is that i believe the default option of CASE SENSITIVE is not the best choice for this particular application and i am doubly annoyed about it because it was not this way in the past - thus rendering previously fully working software "buggy" (in the opinion of end users).

Can you see my point?
thanks,
rob

0
Nikolay Rusev
Telerik team
answered on 30 Mar 2010, 03:00 PM
Hello Rob,

CaseSensitive property of RadGrid for ASP.NET AJAX is introduced on September/2007 and its default value since then is true, which indicates that filtering will be case sensitive.

Can you please tell us in which version of RadGrid for ASP.NET AJAX this property has no affect filter expression or send us sample application demonstrating this behavior?

Regards,
Nikolay
the Telerik team


Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Tags
Grid
Asked by
rdochert
Top achievements
Rank 1
Answers by
Nikolay Rusev
Telerik team
rdochert
Top achievements
Rank 1
Share this question
or