<?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: Nested Navigation Menus - Common Keywords in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25332#M975</link>
    <description>&lt;P&gt;Looking to utilized the uncategorized 'match' option to match terms. So if Dept1 is the first term to match on, the second term would be Keyword1.  The problem is that when I use Keyword1 all of Dept1 and Dept2's searches go under Dept1 &amp;gt; Keyword1.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Feb 2013 00:02:22 GMT</pubDate>
    <dc:creator>BP9906</dc:creator>
    <dc:date>2013-02-12T00:02:22Z</dc:date>
    <item>
      <title>Nested Navigation Menus - Common Keywords</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25330#M973</link>
      <description>&lt;P&gt;Dept1&lt;BR /&gt;
  Keyword1&lt;BR /&gt;
  Keyword2&lt;BR /&gt;
Dept2&lt;BR /&gt;
  Keyword1&lt;BR /&gt;
  Keyword2&lt;/P&gt;

&lt;P&gt;How do I get such a navigation menu to exist using unclassified and 'match'? &lt;/P&gt;

&lt;P&gt;Seems like all Keyword1 matches go to Dept1. &lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2013 15:36:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25330#M973</guid>
      <dc:creator>BP9906</dc:creator>
      <dc:date>2013-02-08T15:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Navigation Menus - Common Keywords</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25331#M974</link>
      <description>&lt;P&gt;Can you clarify what you're looking to achieve here? Are you looking for two layers of navigation or just one?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 00:00:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25331#M974</guid>
      <dc:creator>dart</dc:creator>
      <dc:date>2013-02-12T00:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Navigation Menus - Common Keywords</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25332#M975</link>
      <description>&lt;P&gt;Looking to utilized the uncategorized 'match' option to match terms. So if Dept1 is the first term to match on, the second term would be Keyword1.  The problem is that when I use Keyword1 all of Dept1 and Dept2's searches go under Dept1 &amp;gt; Keyword1.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 00:02:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25332#M975</guid>
      <dc:creator>BP9906</dc:creator>
      <dc:date>2013-02-12T00:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: Nested Navigation Menus - Common Keywords</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25333#M976</link>
      <description>&lt;P&gt;As far as I know, that's not how the matches work. They are straight wildcard matches, and the first match is where the saved search will end up in the menus.&lt;/P&gt;

&lt;P&gt;If you need department and keyword, then include department and keyword in your naming convention and have your submenus use a "Dept1 - Keyword1 - *" type match string in your nav xml.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 00:14:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Nested-Navigation-Menus-Common-Keywords/m-p/25333#M976</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2013-02-12T00:14:07Z</dc:date>
    </item>
  </channel>
</rss>

