It is possible but not trivial. Designer supports XML, SOAP, HTTP name-value pairs and mapping to a database schema. It does not natively support JSON. I suspect you will have to wrap the JSON object in XML, SOAP or a HTTP name-value pair for transport, load a hidden field or the data DOM and then parse the JSON object to map to the form fields.
It is possible but not trivial. Designer supports XML, SOAP, HTTP name-value pairs and mapping to a database schema. It does not natively support JSON. I suspect you will have to wrap the JSON object in XML, SOAP or a HTTP name-value pair for transport, load a hidden field or the data DOM and then parse the JSON object to map to the form fields.
The following has evaluated to null or missing:
==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5]
----