We use this control: Infragistics35.WebUI.UltraWebGrid.v11.1, Version=11.1.20111.1006, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb
Sometimes, there is a bug when saving:
System.Exception: 169.60000610351562 is not a valid value for Int32. ---> System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.ComponentModel.Int32Converter.FromString(String value, NumberFormatInfo formatInfo) at System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) --- End of inner exception stack trace --- at System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) at System.ComponentModel.TypeConverter.ConvertFromInvariantString(String text) at Infragistics.WebUI.Util.Serialization.Serializer.ProcessXmlData(WebControl control, XmlNode node, Object currentObj, Boolean ignoreCase, Boolean reset, XmlNode filterNode) at Infragistics.WebUI.Util.Serialization.Serializer.ProcessXmlData(WebControl control, XmlNode node, Object currentObj, Boolean ignoreCase, Boolean reset, XmlNode filterNode) at Infragistics.WebUI.Util.Serialization.Serializer.ReadLayoutFromXml(XmlTextReader xmlReader, Boolean reset, XmlDocument filterDoc) at Infragistics.WebUI.Util.Serialization.Serializer.LoadFromXml(Object target, String XmlFragment, Boolean reset) at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.LoadPostData(String postDataKey, NameValueCollection values) at System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
I have no idea to fix it.
Please give a help.
The UltraWebGrid was retired in 2011 and hasn't been supported since the spring of 2014.
I see that you are still using the release of 2011 Volume 1 and you may want to test your application with the latest service release as there may be bug fixes that are relevant.
If the latest service release doesn't address the issue, if you are able to provide a sample that reproduces the issue, I will be able to take a look and give you a suggestion on a work around or solution.
If you aren't able to reproduce it in a sample, you may want to download our source code and see if you can debug it on your own to see what specifically is causing the exception. This might give you an idea on a solution or the additional information may help me give you a suggestion.