<?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: I want a dashboard with a &amp;quot;vanity&amp;quot; field dropdown option. A corresponding model number will then be used for the search. in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/I-want-a-dashboard-with-a-quot-vanity-quot-field-dropdown-option/m-p/316309#M20326</link>
    <description>&lt;P&gt;Found a better, faster, simpler (pick 3) way to do this&lt;/P&gt;</description>
    <pubDate>Thu, 30 Nov 2017 21:19:38 GMT</pubDate>
    <dc:creator>dbcase</dc:creator>
    <dc:date>2017-11-30T21:19:38Z</dc:date>
    <item>
      <title>I want a dashboard with a "vanity" field dropdown option. A corresponding model number will then be used for the search.</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/I-want-a-dashboard-with-a-quot-vanity-quot-field-dropdown-option/m-p/316308#M20325</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have the below query, that works just fine.  It searches the data set for a phone model and then displays a more human readable text for the phone model  (example:  Phone model before transforming it to a more human readable format SM-G930F, after transformation, Samsung Galaxy 7).  What I need to do is have the user click on the friendly format and then do a drilldown using the non-friendly format (field=Properties.PlatformData.HM).  I can do the drilldown part just don't know how have the clicked value from the drilldown (friendly format) transformed back into the non-friendly format.  Any thoughts?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=wholesale_app buildTarget=blah analyticType=SessionStart  [search index=wholesale_app buildTarget=blah analyticType=Checkpoint     Properties.index=39 OR Properties.index=40|dedup clientSessionId|table clientSessionId]|lookup phone_models_edited.csv Model AS Properties.platformData.HM
 | stats count  by   Display_model | rename  Display_model as "Phone Model" count as Count|sort -Count
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 30 Nov 2017 20:44:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/I-want-a-dashboard-with-a-quot-vanity-quot-field-dropdown-option/m-p/316308#M20325</guid>
      <dc:creator>dbcase</dc:creator>
      <dc:date>2017-11-30T20:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: I want a dashboard with a "vanity" field dropdown option. A corresponding model number will then be used for the search.</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/I-want-a-dashboard-with-a-quot-vanity-quot-field-dropdown-option/m-p/316309#M20326</link>
      <description>&lt;P&gt;Found a better, faster, simpler (pick 3) way to do this&lt;/P&gt;</description>
      <pubDate>Thu, 30 Nov 2017 21:19:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/I-want-a-dashboard-with-a-quot-vanity-quot-field-dropdown-option/m-p/316309#M20326</guid>
      <dc:creator>dbcase</dc:creator>
      <dc:date>2017-11-30T21:19:38Z</dc:date>
    </item>
  </channel>
</rss>

