Provide some built-in support for commonly used JSON lookups, similar to the way the web viewer is giving users the ability to present information from a number of commonly available sites.
Is there any way this is not redundant with Built-in JSON Functions?
Slightly redundant, yes, but here's the difference. The other discussion is about adding some FUNCTIONS that handle JSON. I'm asking for an initial set of popular JSON that people could build into their solutions very readily.
For example, in the Web Viewer setup we have Mapquest for mapping and FedEx for package tracking and some others. We could have several JSON lookups for zip codes, stock quotes, exchange rates, etc.
So, usage examples of JSON functions in the starter solutions?
I hope not. I get nauseous using starter solutions. I'd rather see an accessory library of languages, expressions, and other tools. SQL Explorer could be thought of as a starter solution for query-building because it allows for cut & paste into solutions but I find myself using it less and less as my skill with SQL grows and instead I'm relying on common libraries of SQL dictionary terms. Same with the app that CNS built for error codes. Maybe the best solution to this is to make the HELP file more robust than it is, or more readily interactive with hyperlinks to functions built into the calc dialog and data viewer?
isn't this available in 16?
Retrieving data ...