All Apps and Add-ons

Multiple TextField

menkurau
Path Finder

I would like to use 2 texfield modules to create a start and end date that is passed to a custom search as arguments. I have only been able to pass a single value thus far from two textfields. Here is an excerpt of the XML

<module name="TextField" layoutPanel="panel_row1_col1" autoRun="True">
  <param name="name">timestamp</param>
  <param name="float">left</param>
  <param name="template">$value$</param>
  <param name="label">Choose today's date (yyyy-mm-dd):</param>
  <param name="default">2013-02-25</param>
  <module name="TextField" autoRun="True">
    <param name="name">timestamp2</param>
    <param name="float">left</param>
    <param name="template">$value$</param>
    <param name="label">Choose future date (yyyy-mm-dd):</param>
    <param name="default">2013-02-25</param>
  </module>
  <module name="SubmitButton">
    <param name="allowSoftSubmit">True</param>
    <module name="Search" layoutPanel="panel_row2_col1" group="Previous Incidents" autoRun="True">
      <param name="search">| script sqlConnInP $timestamp$ $timestamp2$</param>

menkurau
Path Finder

I figured it out, I needed to properly nest the subsequent searches in the submitbutton module.

0 Karma

menkurau
Path Finder

Thanks for the tip! I removed the extra autoRuns as suggested.

0 Karma

sideview
SplunkTrust
SplunkTrust

Yep. I cleaned up your indentation and it became easy to see. Also never nest an autoRun="True" inside another autoRun="True". In this config there should only be one, and it should be on the topmost module -the first TextField. Although it probably wasn't doing specific harm in this particular config, one autoRun nested inside another can wreak havoc and there's never any purpose to doing it.

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 ...