support for large integer in set
I am chasing system owned integers (example, msExchVersion) and I have no problem flowing them into MV and portal by defining custom integer attributes. However, if I use set criteria to say msExchVersion=44220983382016, the request fails. The only reason
seems that it is a large value and nothing else. Any idea why there is this issue with sets being unable to handle large integers?
Anu
June 4th, 2010 2:30am
I tried to create a filter with the same value, and looking into the event log I saw the following error:
System.Data: System.OverflowException: Failed to convert parameter value from a Int64 to a Int32. ---> System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Int64 value)
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType)
--- End of inner exception stack trace ---
Maybe you should submit a bug on connect?
Paolo Tedesco - http://cern.ch/idm
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2010 10:33am
Hi Anu,
Is there a reason why you need an integer attribute specifically? If you're not creating sets that require greater than or less than operators, you could flatten the integer into a string attribute instead.
Do file a bug on Connect. Seems like we have an issue with parsing int64s for set filters.
Billy
June 4th, 2010 9:42pm