I have a number of grids that use an UnboundCheckBoxField to enable selection for processing. It was working fine with the standard 2013.1 release version, but after updating with SR 2045 I am now getting a RequestValidationException ("A potentially dangerous Request.Form value was detected from the client") sometimes when I click some of the checkboxes. Specifically, it seems to happen when losing focus of a checkbox after toggling it. It happens on every grid where I have this and it was working just fine before the SR.
I know I could turn off page request validation but I would prefer to leave it on if possible.
Any ideas? For the meantime I am going to drop back down to the 2013.1 release version, but I would like to be able to stay up-to-date if possible.
Thanks!
Hi Philip,
Can you please add a sample?
Thanks
Olga
Hello Philip,
Is there any specific logic executed when you click on checkboxes in this application?
Also if you use the following sample - http://es.infragistics.com/products/aspnet/sample/data-grid/unbound-checkbox-column - do you get the same exception?
If no can you attach a small sample showing this behavior as Olga requested?
On one page, we have client-side handlers for the cell edit and header checkbox click events, but on another page we do not. Both pages behave the same way and have the issue.
I had to uninstall/reinstall to revert back to the 2013.1 release version in order to continue working for the moment. I will try to apply the SRs one at a time (I have 2012 and 2045) and test the pages one day later this week and get back to you. I will also try the suggested sample and putting together an example.
Thank you for your feedback.
You can update us with the testing results once ready and if the same issue is present again attach the sample so we can debug it locally.
We have finally been able to reproduce this exception. It appears in the latest SR and not in RTM version as you pointed.
I have created a Support Case in your behalf (CAS-117464-Y5V5J2) and it will be linked with the Development Issue logged for this behavior - 144084.
Thank you for your cooperation.
Excellent, I am glad you were able to reproduce it without my sample. Thank you for following up with this.
We are still following up this case. If you have more questions, concerns or suggestions don’t hesitate to contact us again.
Hello,
This issue has been fixed with the latest Service Release for 12.2 and 13.1.
The Service Release is available for download from your account's "My Keys & Downloads" page.