RESOLVED Input string was not in a correct format error due to saved Signature format


Logging into AyaNova results in the following error Input string was not in a correct format

And in your ayalog.txt file:
2013-09-20 12:50:02,372 [3308] FATAL AyaNova.Form1 - Unhandled exception
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —>
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Int32.Parse(String s)
at GZTW.AyaNova.BLL.AySignature.A(String A)
at GZTW.AyaNova.BLL.AySignature.B()
at GZTW.AyaNova.BLL.AySignature.get_SignatureBitmap()
at GZTW.AyaNova.BLL.AySignature.get_SignatureBitmapAsByteArray()
at GZTW.AyaNova.BLL.WorkorderServiceList.DataPortal_Fetch(Object Criteria)
— End of inner exception stack trace —

ayalog.txt shows that the code is throwing an invalid format exception in aySignature StringToPoint method on int.parse

Troubleshooting narrowed the issue down to one workorder
Further troubleshooting narrowed it down that the signature x y coordinates were each a decimal rather than a whole integer.

Apparently one or more devices or browsers saved the signature HTML5 coordinates as fractions rather than whole numbers.

Development has released a hotfix 10 for the GTZW.AyaNova.BLL.dll with code to check for the presence of a decimal point in the string that represents the x/y coordinate pairs of the signature points. So in cases where there is a decimal point AyaNova will use a different method of parsing the strings to Points ( signatures without decimals which is the norm, will be parsed exactly as before to ensure less chance of side effects)