There was a readOnly access on the subform that holds the TextField.
I remember there being an issue over a year ago where under a specific set of circumstances that could happen to you. Note that there is no UI in designer to remove that so I had to do it in the XML source. Here is the updated sample.
There was a readOnly access on the subform that holds the TextField.
I remember there being an issue over a year ago where under a specific set of circumstances that could happen to you. Note that there is no UI in designer to remove that so I had to do it in the XML source. Here is the updated sample.
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]
----