When adding a BoundCheckBoxField on a WebDataGrid I can not uncheck the checkboxes that are already checked (the ones that have "true" as value). There are no problems with the unchecked ones (those that have "false" as value).
It seems that the checked checkboxes are readonly and I cant find where to change that property.
The behaviour that I'm facing is the same as this sample http://es.infragistics.com/samples/aspnet/data-grid/checkbox-column. In that sample, you cannot change the checked values (Column "Discontinued").
Hello Mauricio,
Thank you for contacting Infragistics!
I have done some testing and I have been unable to reproduce the issue in an isolated sample. I am using version 14.1.20141.2150 of the Infragistics for ASP.NET 2014 Volume 1 product. What version are you using? I am attaching my sample to this thread, please run the sample and let me know what the result is. What version of the Infragistics product are you using including service release? Do you have an isolated sample that reproduces this issue? Note that in my sample I removed the ig_res folder for file size to be attached to this thread.
Hello Mike,
I'm able to run your code. But the problem persists with some extra bonus.... The column "Partner" is totally locked, I cannot change the state of any checkbox in that column. The column "OnSite" is where the problem I described in my original post occurs.
I'm using Version=14.1.20141.1015
I have attached a document with some screenshots and also the webpage, codebehind and web.config.
I would appreciate any guidance and help.
Thank you for the update. I have done some further looking into this matter and your sample. First you are unable to editing the “Partner” column as the column is marked as read only. I did this to best represent the sample you linked previously. Next when I use service release 1015 of v14.1 I am able to reproduce this issue. When I upgrade my sample to 2150 I am no longer able to reproduce the issue. This means that at some point between a fix was made for this issue. I recommend you upgrade to the latest service release of v14.1.
Thanks!!
Upgrading did the trick.