Installation

Forms/Views behaviour after Splunk 6 Upgrade

mantockd
Explorer

I have just upgraded to Splunk 6.0. When I do a form search it has completely different behaviour in comparison to Splunk 5.

In Splunk 5 blank fields were like behaving as if there was * in the search query and all results were returned. Now if I do the same thing in Splunk 6.0 I get this error:

Search query is not fully resolved.

Even when I just launch the view I get the same error.

mantockd
Explorer

Yes this is

flavor of Simple XML

0 Karma

melting
Splunk Employee
Splunk Employee

Yeah this is a subtle change in the two versions

To work around use an empty default:

<input type="text" token="get3">
    <label>Get from drilldown: Count</label>
    <default></default>
</input>

mantockd
Explorer

I should have more accurately stated, this does solve the problem when searching, if I take * as the default, but the problem still remains on launching the form.

0 Karma

mantockd
Explorer

flavor of Simple XML

0 Karma

melting
Splunk Employee
Splunk Employee

What is your xml?

0 Karma

mantockd
Explorer

This did not resolve the problem.

0 Karma

sideview
SplunkTrust
SplunkTrust

Is this view written in the <form> flavor of Simple XML?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...