Not that I am aware of .....it tries to bind the imbound field to the field named on the form and if it can you will see your data ...otherwise it will not appear.
It is assumed that the inbound data has been validated against the schema before the import is done hence there should not be data type mismatches.
Not that I am aware of .....it tries to bind the imbound field to the field named on the form and if it can you will see your data ...otherwise it will not appear.
It is assumed that the inbound data has been validated against the schema before the import is done hence there should not be data type mismatches.
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. (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]
----
