Jeff, I usually specify the type as well. But, and I haven't rigourously tested this, I think you're more likely to get those errors with a c-obj parsed from a string. I think when 4D encodes it there's no ambiguity but when parsing a string since JSON isn't type strictly it can happen.
On Thu, Apr 27, 2017 at 2:59 PM, Jeffrey Kain via 4D_Tech < [email protected]> wrote: > Have others experienced 4D being unable to correctly determine the type of > a variable when assigning it from an OB GET, if you don't specify the type > of variable (i.e. "is text", "is longint", and especially "is object")? > -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
