I'm surprised how little discussion there is of this issue in the forums and the docs. At which release is this fixed? I'm at 10.1 with the problem. What value does Number.NaN translate to in the JSON request? Does this workaround work for a nullable attribute of any GDB data type? What is the workaround from Silverlight?
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.