I have a grid with filtering turned on. All my filters work great except my date column. Here is the column:
When I pick a date on the calendar and click the filter icon and choose a filter, a javascript error shows in the status bar that says the following:
Sys.Webforms.PageRequestManagerErrorException: Index (zero based) must be greater than or equal to zero and less than the size of the arguement list. Code: 0.
Of course the filter doesn't take affect.
Anything I'm missing?
| <telerik:GridDateTimeColumn DataField="MedicalRenewalDate" HeaderText="Renews" |
| SortExpression="MedicalRenewalDate" UniqueName="column9" |
| DataFormatString="{0:d}" FilterControlWidth="90px" PickerType="DatePicker"> |
| </telerik:GridDateTimeColumn> |
When I pick a date on the calendar and click the filter icon and choose a filter, a javascript error shows in the status bar that says the following:
Sys.Webforms.PageRequestManagerErrorException: Index (zero based) must be greater than or equal to zero and less than the size of the arguement list. Code: 0.
Of course the filter doesn't take affect.
Anything I'm missing?
6 Answers, 1 is accepted
0
Hi drpcken,
Version 13.14 of RadGrid does have this filtering issue which has already been fixed. You can download the fix from your customer account under latest builds.
Hope this helps.
Best regards,
Tsvetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Version 13.14 of RadGrid does have this filtering issue which has already been fixed. You can download the fix from your customer account under latest builds.
Hope this helps.
Best regards,
Tsvetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
drpcken
Top achievements
Rank 1
Rank 1
answered on 01 Mar 2009, 10:20 PM
I am currently on version 1314.
I've noticed it only seems to happen with the datetime column type, if I replace it with a bound column it seems to work fine.
I've noticed it only seems to happen with the datetime column type, if I replace it with a bound column it seems to work fine.
0
Accepted
Hello drpcken,
In case you use .NET 35 version of the grid, can you check whether setting EnableLinqExpressions = false for the control makes a difference? You may also test with the latest internal build from your account to see whether this addresses the error in question.
Kind regards,
Sebastian
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
In case you use .NET 35 version of the grid, can you check whether setting EnableLinqExpressions = false for the control makes a difference? You may also test with the latest internal build from your account to see whether this addresses the error in question.
Kind regards,
Sebastian
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Brett Robichaud
Top achievements
Rank 1
Rank 1
answered on 05 Mar 2009, 01:03 AM
I am experiencing this same problem with the 2008.3.1314.35 build. I can confirm that if I set EnableLinqExpressions to false the problem is resolved. I am curious what I lose by disabling this however? And is there a fix in the works that doesn't require disabling linq expressions?
0
drpcken
Top achievements
Rank 1
Rank 1
answered on 05 Mar 2009, 03:47 AM
That worked for me! I'm glad it fixed it, but I'm curious also why I have to disable Linq on the grid...
0
Shinu
Top achievements
Rank 2
Rank 2
answered on 05 Mar 2009, 07:36 AM
Hi All,
I have found somewhere in the Help articles regarding the EnableLinqExpressions stating:
With the .NET 3.5 build of RadGrid for ASP.NET AJAX and LINQ filter expressions enabled (EnableLinqExpressions = true), the filter expressions set for the grid either internally by its filtering mechanism or manually in code should conform to the LINQ expression syntax instead of the old T-SQL syntax. Only thus they will be evaluated properly by the control.
Thanks
Shinu
I have found somewhere in the Help articles regarding the EnableLinqExpressions stating:
With the .NET 3.5 build of RadGrid for ASP.NET AJAX and LINQ filter expressions enabled (EnableLinqExpressions = true), the filter expressions set for the grid either internally by its filtering mechanism or manually in code should conform to the LINQ expression syntax instead of the old T-SQL syntax. Only thus they will be evaluated properly by the control.
Thanks
Shinu