> On 27 Jul 2017, at 15:43, Epperlein, Lutz (agendo) via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> OK, found it. It is possible. (To be honest, I didn't expect anything else)
>
> The only question is now, how do I combine the code developed using 4D's
> object commands with the NTK JSON
> The result should be:
> { "values": [
> [ 4711 ]
> ] }
>
> Is this possible too?
OK, found it. It is possible. (To be honest, I didn't expect anything else)
The only question is now, how do I combine the code developed using 4D's object
commands with the NTK JSON API?
E.g., I have a
ux
> via 4D_Tech
> Sent: Thursday, July 27, 2017 2:35 PM
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Cc: Rob Laveaux <rob.lave...@pluggers.nl>
> Subject: Re: 2dim json arrays with scalar values
>
>
> > On 27 Jul 2017, at 14:09, Epperlein, L
Hi,
Maybe it is related to the recent discussion pro and contra the quality of 4D's
JSON implementation. I think I found a serious problem, a real limitation of
4D's JSON.
4D's JSON resp. object implementation is able to handle arrays, so far, so
good. But even the doc states that it doesn't
4 matches
Mail list logo