<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Extended field search ordering in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Extended-field-search-ordering/m-p/46187#M2260</link>
    <description>&lt;P&gt;I think the best place to start would be the UI Examples app:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunkbase.splunk.com/apps/All/4.x/Add-On/app:Splunk+UI+examples+app+for+4.1%2B" rel="nofollow"&gt;http://splunkbase.splunk.com/apps/All/4.x/Add-On/app:Splunk+UI+examples+app+for+4.1%2B&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;That should have plenty of examples of how to work intentions for this type of a situation. Specifically, I'd take a look at form3 (/en-US/app/ui_examples/form3) which is labeled "inverted flow, panel-defined search" in the nav, and "Multi-panel linked form search" on the actual page. That sounds like what you want to do.&lt;/P&gt;

&lt;P&gt;Hope that's helpful. &lt;/P&gt;</description>
    <pubDate>Fri, 18 Feb 2011 03:20:40 GMT</pubDate>
    <dc:creator>David</dc:creator>
    <dc:date>2011-02-18T03:20:40Z</dc:date>
    <item>
      <title>Extended field search ordering</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Extended-field-search-ordering/m-p/46186#M2259</link>
      <description>&lt;P&gt;I would like to display a textbox where users can enter the username and click on submit. The results  to be displayed are saved search for the username,last 5 searches,Roles(from a lookupfile) and last login information.&lt;/P&gt;

&lt;P&gt;I am not sure the kind of Intentions to use and the ordering of the HiddenSearch and ExtendedFieldSearch modules. I just want the user to click submit once and replace the username field in all the searches to be replaced with the value from the textbox.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2011 19:42:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Extended-field-search-ordering/m-p/46186#M2259</guid>
      <dc:creator>sanju005ind</dc:creator>
      <dc:date>2011-02-17T19:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: Extended field search ordering</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Extended-field-search-ordering/m-p/46187#M2260</link>
      <description>&lt;P&gt;I think the best place to start would be the UI Examples app:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunkbase.splunk.com/apps/All/4.x/Add-On/app:Splunk+UI+examples+app+for+4.1%2B" rel="nofollow"&gt;http://splunkbase.splunk.com/apps/All/4.x/Add-On/app:Splunk+UI+examples+app+for+4.1%2B&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;That should have plenty of examples of how to work intentions for this type of a situation. Specifically, I'd take a look at form3 (/en-US/app/ui_examples/form3) which is labeled "inverted flow, panel-defined search" in the nav, and "Multi-panel linked form search" on the actual page. That sounds like what you want to do.&lt;/P&gt;

&lt;P&gt;Hope that's helpful. &lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2011 03:20:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Extended-field-search-ordering/m-p/46187#M2260</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-02-18T03:20:40Z</dc:date>
    </item>
  </channel>
</rss>

