All Apps and Add-ons

Does an ExtendedFieldSearch module in a Search module work?

joy76
Path Finder

Hi everyone~

i'm using URLLOADER. then i send a parameter to a view (VIEW1) by url.

http://splunkhost:8000/app/MyApps/VIEW1?parameter=value

so, i have to use Search module not HiddenSearch module. HiddenSearch module can't receive the parameter from a url by URLLOADER isn't it?

The VIEW1 has a Search module, a StaticSelect module, two ExtendedFieldSearch modules and TimeRangePicker module.

Its structure is like below.

<view>
  <module URLLOADER>
    <module Search>
      <param search>...$parameter$...$parameter1$...$parameter2$...$parameter3$...</param>
        <module StaticSelect >
          <param>parameter1</param>
            <module ExtendedFieldSearch >
              <param>parameter2</param>
                <module ExtendedFieldSearch >
                  <param>parameter2</param>
                    <module TimeRangePicker>
                      ...
                      <module SimpleResultsTable>
    ......
0 Karma

sideview
SplunkTrust
SplunkTrust

If you haven't looked at it already, go to the Sideview Utils documentation and check out

a) the notes about the 'Search' module. The page is called 'The Search module - (aka life without intentions)' and it's one of the most important pages to read.

b) the pages under the section about 'linking'.

Actually even if you have looked at them already, I think you should still go back and take a closer look.

There are a number of things that it says to do on these pages that you're not doing.

1) the Search module has to live downstream from the form element modules whose input contribute to the search. (this is the #1 bullet on the 'Search' page)

2) While you can in some scenarios mix old modules like StaticSelect in with new Sideview modules, it's not recommended, you lose a lot of features (like prepopulation from the URL) and there's really no reason to. Use Pulldown instead of StaticSelect.

and then there are some things that my docs don't explicitly state, but which perhaps they should:

3) ExtendedFieldSearch creates an 'intention' which is a pretty fundamental point of incompatibility with the Sideview modules. Use TextField instead. ExtendedFieldSearch really offers no benefit over TextField.

4) ExtendedFieldSearch, StaticSelect, SearchSelectLister cannot be prepopulated by the URLLoader module. The only core Splunk UI modules that can be prepopulated by URLLoader are SearchBar and TimeRangePicker.

Hope that helps.

joy76
Path Finder

Thanks nick!

I appreciate for your help. always.

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!

Observability Simplified: Combining User Experience, Application Performance & ...

Tech Talk Observability Simplified: Combining User Experience, Application Performance & Network ...

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...