<?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 Dashboard click to another but keep dasboard (radio) params in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Dashboard-click-to-another-but-keep-dasboard-radio-params/m-p/289290#M18333</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;

&lt;P&gt;So, now we are faced with keeping and/or parsing the radio button selection/value (i.e. dev, prod, qa, etc.) to the next dashboard when selecting or drilldown in a dashboard.  I attempted removing the &lt;CODE&gt;&amp;lt;default&amp;gt;&lt;/CODE&gt; value from the XML but that didn't seem to get any results.  Any thought or ideas are greatly appreciated...&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Leo&lt;/P&gt;</description>
    <pubDate>Thu, 11 May 2017 22:25:57 GMT</pubDate>
    <dc:creator>leomedina</dc:creator>
    <dc:date>2017-05-11T22:25:57Z</dc:date>
    <item>
      <title>Dashboard click to another but keep dasboard (radio) params</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Dashboard-click-to-another-but-keep-dasboard-radio-params/m-p/289290#M18333</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;

&lt;P&gt;So, now we are faced with keeping and/or parsing the radio button selection/value (i.e. dev, prod, qa, etc.) to the next dashboard when selecting or drilldown in a dashboard.  I attempted removing the &lt;CODE&gt;&amp;lt;default&amp;gt;&lt;/CODE&gt; value from the XML but that didn't seem to get any results.  Any thought or ideas are greatly appreciated...&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Leo&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2017 22:25:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Dashboard-click-to-another-but-keep-dasboard-radio-params/m-p/289290#M18333</guid>
      <dc:creator>leomedina</dc:creator>
      <dc:date>2017-05-11T22:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: Dashboard click to another but keep dasboard (radio) params</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Dashboard-click-to-another-but-keep-dasboard-radio-params/m-p/289291#M18334</link>
      <description>&lt;P&gt;Hi @leomedina,&lt;BR /&gt;
If I'm understanding your question correctly, it sounds like you can set a token in your target dashboard (the one that opens when a user clicks on the drilldown) to the selected value from the source.&lt;/P&gt;

&lt;P&gt;Use the token that represents the selected value in the source, and pass that value to the target as part of the drilldown. Depending on where that value should propagate, set the appropriate token in the target to that selected value. &lt;/P&gt;

&lt;P&gt;Something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  &amp;lt;drilldown target="blank"&amp;gt;
       &amp;lt;!-- Access the input on the target form, which is in the same app  --&amp;gt;
       &amp;lt;!-- sourcetype.tok is the token for an input to the target form    --&amp;gt;
       &amp;lt;link&amp;gt;
          form_for_drilldown?form.sourcetype_tok=$click.value$
        &amp;lt;/link&amp;gt;
      &amp;lt;/drilldown&amp;gt;  
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;See &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.0/Viz/DrilldownLinkToDashboard"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.0/Viz/DrilldownLinkToDashboard&lt;/A&gt; for more info in our docs. &lt;/P&gt;

&lt;P&gt;Hope that helps!&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2017 22:55:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Dashboard-click-to-another-but-keep-dasboard-radio-params/m-p/289291#M18334</guid>
      <dc:creator>frobinson_splun</dc:creator>
      <dc:date>2017-05-11T22:55:48Z</dc:date>
    </item>
  </channel>
</rss>

