Hi @neelay: I’m glad the workaround you found in the post you mentioned got you the result that you were looking for. I believe that your question about if this is an expected behavior or not will be determined by the input field’s data type. The parseJSON functions documentation mention the function expects different data types, based on the “dialect”. It could be that you are seeing some implicit conversion of your JSON to a string. Could you please confirm the source dialect and data type?
Thanks.
Chris