topic Re: Replacement for list and module elements? in Splunk Dev

Replacement for list and module elements?

pbankar — Thu, 27 Jul 2017 08:36:59 GMT

Team,

Need help to upgrade the list and module elements from the simple search page to the latest update.
Or how can I create a new type of search page which can be embedded in my app?

Re: Replacement for list and module elements?

martin_mueller — Thu, 27 Jul 2017 09:09:00 GMT

AdvancedXML has been officially deprecated for almost two years: http://docs.splunk.com/Documentation/Splunk/6.6.2/AdvancedDev/Whatsinthismanual#Advanced_XML_Deprecation
If you're developing things based on AdvancedXML you have two reasonable options, go with sideview's branch of AdvancedXML or switch to Splunk's SimpleXML.

Regarding your search page, there is a new search page since 6.0 called drumroll search. You can use that in your app, it's shared globally from the default search app.

Re: Replacement for list and module elements?

pbankar — Thu, 27 Jul 2017 09:11:54 GMT

Thanks martin_mueller

Re: Replacement for list and module elements?

pbankar — Fri, 28 Jul 2017 10:35:59 GMT

@martin_mueller can you please suggest any relevant link for embedding the drumroll search in any dashboard?

Re: Replacement for list and module elements?

martin_mueller — Fri, 28 Jul 2017 11:50:42 GMT

search is the default search view, you can link to it from within any app as long as the user can see the search app. You can't easily embed it as part of another dashboard.

Re: Replacement for list and module elements?

pbankar — Fri, 28 Jul 2017 11:53:34 GMT

Actually, I need to create a replica of the Search & Reporting in my app where the user can search the app related queries. Is there anyway?

Re: Replacement for list and module elements?

martin_mueller — Fri, 28 Jul 2017 12:42:28 GMT

Why do you need a replica? Including the search view in your app's navigation menu will let you use it without duplication.

Re: Replacement for list and module elements?

pbankar — Tue, 29 Sep 2020 15:09:47 GMT

@martin_mueller, thanks for the highlight.
I tried to redirect to app/search/search from my app's navigation but the URL its forming is - http://ip:8000/en-GB/app/my_app_name/app/search/search. It's not getting out of my app's environment. Can you please suggest something.

Re: Replacement for list and module elements?

martin_mueller — Mon, 31 Jul 2017 08:09:26 GMT

Simply referring to the view's name, search, is enough for the navigation menu:

  <view name="search" />

Re: Replacement for list and module elements?

pbankar — Tue, 29 Sep 2020 15:09:50 GMT

@martin_mueller, thanks for the quick response. even I tried an anchor tag way-

<a href="/app/my_app_name/search?q=search%20index%3D_internal">Search</a>

This way I can get a default searchquery but the problem is the "/my_app_name/" .
I have different apps and don't want to hardcode the app name. Do you have any solution for this?

Re: Replacement for list and module elements?

pbankar — Mon, 31 Jul 2017 08:30:52 GMT

I tried -

    <view name="search" >index=_internal</view> 
    <view name="search" ><default>index=_internal</default></view>

But these are invalid default searches. Any better way?

Re: Replacement for list and module elements?

martin_mueller — Mon, 31 Jul 2017 08:43:35 GMT

The nav xml schema doesn't have any sub- or text-elements inside a view element, so that can't work.

If you need to pass parameters to the search view - first time you mention this... 😛 -, you need to use the a element, something like this:

<a href="search?q=index%3D_internal">Search the _internal index</a>

This relative link doesn't need to know the app name it's in, it just stays where it is.

Re: Replacement for list and module elements?

pbankar — Mon, 31 Jul 2017 09:16:37 GMT

Thanks @martin_mueller. It worked.