Dashboards & Visualizations

Dashboard not loading with error, "totalQuery is undefined"

sylim_splunk
Splunk Employee
Splunk Employee

Some of my dashboards are not loading after the 7.3.x upgrade - which were all Okay with the previous version was 7.2.6.
The error messages are different from browsers but common thing is, the dashboards are not loading with the errors.
Errors are, as below with invalid line numbers.

totalQuery is undefined or

undefined is not an object (evaluating 'totalQuery.replace')

Tags (1)
1 Solution

sylim_splunk
Splunk Employee
Splunk Employee

This is caused by some post-process searches, such as if a post-process search doesn't contain <query> element, then dashboard is not loading. This is due to JavaScript undefined error. And can be worked around by adding empty query element for the post-process searches without query. This is just a temp workaround and may not be needed once fixed (7.3.4+, 8.0.1+).

for example, below is Okay
<search base="callsA" id="myTable">
<query>
| search call_id="$token1$"
...<SNIP>
</query>
</search>

But if a post-process search doesn't have any query but only has some options, which will cause the error/symptoms (SPL-178012).
<search base="callB" id="yourTable"></search>

It can be worked around by adding empty query element as below.

<search base="callB" id="yourTable">
<query></query>
</search>

View solution in original post

sylim_splunk
Splunk Employee
Splunk Employee

This is caused by some post-process searches, such as if a post-process search doesn't contain <query> element, then dashboard is not loading. This is due to JavaScript undefined error. And can be worked around by adding empty query element for the post-process searches without query. This is just a temp workaround and may not be needed once fixed (7.3.4+, 8.0.1+).

for example, below is Okay
<search base="callsA" id="myTable">
<query>
| search call_id="$token1$"
...<SNIP>
</query>
</search>

But if a post-process search doesn't have any query but only has some options, which will cause the error/symptoms (SPL-178012).
<search base="callB" id="yourTable"></search>

It can be worked around by adding empty query element as below.

<search base="callB" id="yourTable">
<query></query>
</search>

Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...