I just happened to notice that using the 'Contains' filter with text containing an apostrophe doesn't seem to work.
In my example, I show an entry in my grid called "Ryan's Template". Entering "Ryan's", and using the "Contains" or "StartsWith" filters reduces my grid to show the NoRecordsTemplate.
I also tried "Ryan''s" and "Ryan\'s", thinking maybe filtering wasn't escaping, no luck.
Maybe a bug in the filtering? Running just character filters always seems to work (like filtering down to "Ryan", for example).
In my example, I show an entry in my grid called "Ryan's Template". Entering "Ryan's", and using the "Contains" or "StartsWith" filters reduces my grid to show the NoRecordsTemplate.
I also tried "Ryan''s" and "Ryan\'s", thinking maybe filtering wasn't escaping, no luck.
Maybe a bug in the filtering? Running just character filters always seems to work (like filtering down to "Ryan", for example).
2 Answers, 1 is accepted
0
Hello Scott,
Could you please go to the online demo shown below and try to find the La maison d'Asie item in the ShipName column using this string -> d\'Asie
Basic filtering
Regards,
Daniel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Could you please go to the online demo shown below and try to find the La maison d'Asie item in the ShipName column using this string -> d\'Asie
Basic filtering
Regards,
Daniel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
golddog
Top achievements
Rank 1
Rank 1
answered on 06 Oct 2008, 10:07 PM
We did notice something on this today. The service we used to get the data returned IEnumerable<Whatever>, which we then did a .OrderBy on, then set that as the grid's data source.
The .OrderBy made our IEnumerable into an IOrderedEnumerable, which the grid wouldn't filter. Moving the ordering back into the linq query in the service worked for this instance.
I wouldn't say I'm sure why making this change allowed the grid to filter, but it seemed to get us going in this case.
The .OrderBy made our IEnumerable into an IOrderedEnumerable, which the grid wouldn't filter. Moving the ordering back into the linq query in the service worked for this instance.
I wouldn't say I'm sure why making this change allowed the grid to filter, but it seemed to get us going in this case.