We just upgraded to 9.2 build 2056 and our embedded controls no longer change the cell value in the grid.
I have a attached a small example web site showing this behavior.
From the posting, I understand that the issue is regarding WebDateChooser as Editor for Cell in WebGrid did not update the cell value.
I got my service release(Version=9.2.20092.2099) but the cell value is not getting updated. The basis of my observation is that the UpdateCell event of the WebGrid does not fire when I update the date (I assign a default date when I add a new row). I switched to WebDateTimeEdit. The behavior is same. What I also observe with WebDateTimeEdit is that the UpdateCell event fires only if the cell is set to empty (has value null).
How can I update my cell value with one of these EditorControls?
Thank you!
<edit>
Please ignore this post. I had the workaround for FF 3.6 in my project and after intalling the service release, I forgot to update the Scripts folder in my project.
The EditorControl (WebDateChooser) works as documented.
</edit>
Hello Andrew,
There is a planned date. You can refer the official release calendar by following this link:
http://ko.infragistics.com/support/service-releases.aspx#ServiceReleases
For ASP.NET the scheduled date is 5 April for 9.1 and 9.2 versions.
With regards,
Thanks to everyone for their feedback.
@Rado:
Is there a release date when there will be a fix available? This is a critical part of our software and we are close to a release, we need to have this functionality available.
Hello Guys,
I would like to inform you that this issue is already reported and we are taking actions to fix it.
Thank you for the feedback!
I reverted back to the previous release (1003). I cannot believe they would release something to the public that would break this badly. I can't understand why this hasn't been identified by more people as I'm sure putting dates in grids isn't something just a few of us do.
I have been a subscriber for over 6 years and have finally decided I can't deal with Infragistics issues from release to release as I have in the past. We are slowly moving off this platform as our business can't take this any longer.