I am using EntityDataSource for binding Grid. it is working fine. but while filtering CaseSensitive=False is not working. i am using Oracle Database for Model. i set the property like "<GroupingSettings CaseSensitive="False" />". but still not working. please let me know ASAP.
Thanks in Advance,
Dhamu
11 Answers, 1 is accepted
The RadGrid does not perform the filtering itself, it just pass the arguments to your DataSource. And the Filtering is happening in either your DataSource or your Database.
The CaseSensitive property of the RadGrid is used only to be set as CaseSensitive to the DataTable in case the grid is bound to such.
To resolve your issue I would suggest you to debug your DataSource and see if the filtering is happening inside it or in your DataBase. Profile the queries to your database and if needed modify your database server. It should have some configurations for IgnoreCase in your Database.
Regards,
Vasil
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Thanks for you reply. i am using same functionality using SqlDataSource, filter functionality working without Case Senesitve. but not in EntityDataSource. please check my attached image. is there any solution for this one?
Thanks in Advance,
Dhamu
Can anyone help about that one?. I want this option for my Project. Please help ASAP.
Thanks in Advance,
Dhamu
I have researched on this problem. Since the EntityDataSource does not have any functionality to ignore the case, we will need to modify the build FilterExpresssion by the grid.
I have logged this as future request in our internal tracking system and we will try to improve it for our next service pack.
Currently I do not see any workaround that can be used, especially with Oracle database (if I read correctly in the oracle related forums, the tables can not be made to be case insensitive when selecting).
Regards,
Vasil
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Hi Vasil,
I checked this functionality in latest version 2015 Q2. it is not fixed yet. may i know the update about this one?
I have checked in our internal system and it seems that the bug in question is still not fixed. However, for your convenience I have increased the priority of the item, so our developers team could take a look at the bug as soon as possible.
Please excuse us for any inconvenience caused by the delay.
Regards,
Konstantin Dikov
Telerik
Hey Telerik Team,
This issue very very disappointed for us. we are not able to answering our client. In this case how can i tell with my client only use Upper Case or Lower Case or Mixed Case.
If you can say your client like this?
Common guys, our Company asking this question from 2 years before but you did not anything for this issue. so i can't tell any answer for my manger and client.
We are using your software so you want response this one. Please help us immediately to fix this issue.
Its very very very important for us, Please help
Thanks,
Hi Telerik Team,
Can anyone response?. Please let us know ASAP
Thanks,
The logged item is still in evaluation and there is still no workaround that could be used. The only thing that I could suggest you to try is to set the GroupingSettings-CaseSensitive property of RadGrid to "false" and see if it will make any difference with the filtering.
I have logged a public item related to the one that we already have in our internal system, where you could follow its progress:
Best Regards,
Konstantin Dikov
Telerik
Hello,
I know it's an old case, but does anyone knows if this issue was eventually resolved? Or was any workaround proposed?
I'm asking, because I think I've encountered the same problem recently.
The link above is down btw (http://feedback.telerik.com/Project/108/Feedback/Details/174038-ignorecase-property-of-radgrid-does-not-have-effect-when-bound-to-entitydatasourc)
The issue in this thread has not been fixed due to its low priority. I have make a new public item for the bug, so you can track its progress and vote in order to increase its priority here:
https://feedback.telerik.com/aspnet-ajax/1400886
Regards,
Vessy
Progress Telerik