TeamDesk Knowledge Base & Support

basenine 4/15/2021 1:29:58 AM

@Pierre,
I think this is a new implementation (Early March)...Like URLEncode(), you can now use JSONEncode().

See here:
https://www.teamdesk.net/blog/whats-new/passthrough-blocks-in-call-url-and-navigate-actions/
Best regards,
Brett

Pierre 4/15/2021 3:14:05 AM

@Brett

Thanks a lot for your recommendation - you are correct, JSONEncode and <%* do help a lot.
But they are still a bit tricky to use.

Why not having proper JSON functions to process the data ?
- In JSON data building sense
- as well as in JSON data retrieving sense:
ex if you need to retrieve an object including an array of objects
{
"item1": ...,
"array0": [{object 0}, {object 1}, ...]
}
1) Response() refuses (I might be mistaken as always) to retrieve array0 as a whole
2) It would be nice to store array0 somewhere, and then deal with its constituants later without having to build a table/ subtable to store the data (upsert is useful)

Kind regards,

Pierre

basenine 4/15/2021 3:33:03 AM

Yes. It took me a day to configure a working array from a child list. It involved stringing multiple List()together, then concatenating them...then Left() this and Right() that...Replace() was used at least once, too
🤣🤣

Pierre 4/19/2021 10:46:02 AM

A first step might be to allow Response() to :
- process Multiline Text fields
- retrieve complex objects (Arrays, Objects) rather than only single (text, numeric,...) fields