You need to schedule spikes for the Parent Report Suites if there is an expected change in traffic as Virtual Report Suites derives data from the parent report suites.
You need to schedule spikes for the Parent Report Suites if there is an expected change in traffic as Virtual Report Suites derives data from the parent report suites.
The following has evaluated to null or missing:
==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31]
----
Tip: It's the final [] step 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 acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5]
----
