All Apps and Add-ons

How to reload SideView TextField

richnavis
Contributor

I've created a view using sideview 2 dynamic sideview pulldowns and a textfield. The user chooses values from the pulldowns, then enters a value of his choosing in the textfield, then chooses a timeerange from the timepicker, then the submit button. This works fine for a single search, but if the user changes only the textfield and searches again, the search produces the same results. It seems the only way for the textfield to push updated values to the downstream searches, the user must refresh the page by changing one of the pulldowns. Is there a way to have the page autorefresh data from the textfield without having to re-choose the pulldowns?

0 Karma
1 Solution

sideview
SplunkTrust
SplunkTrust

This is a good question. I'm quite familiar with this and as of long-ago improvements to the TextField module, the problem became much harder to hit, but it's still there in certain specific cases.

To make a long story short, I'll bet that your Search module that ties all of this together, is upstream from the Button module. Change that so that the Search module is downstream from the Button, and the bug will go away. The change will have no other practical effect on the view. It's possible if you have an extremely complex view (i do not say this lightly), that you can hit the bug in other ways, but I think this simple change will fix your problem. Let me know how it works.

View solution in original post

sideview
SplunkTrust
SplunkTrust

This is a good question. I'm quite familiar with this and as of long-ago improvements to the TextField module, the problem became much harder to hit, but it's still there in certain specific cases.

To make a long story short, I'll bet that your Search module that ties all of this together, is upstream from the Button module. Change that so that the Search module is downstream from the Button, and the bug will go away. The change will have no other practical effect on the view. It's possible if you have an extremely complex view (i do not say this lightly), that you can hit the bug in other ways, but I think this simple change will fix your problem. Let me know how it works.

richnavis
Contributor

That did the trick!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...