<?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 Drilldown - Passing along equals (=) and quotes (&amp;quot;) in parameter values in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183098#M11286</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am using SideView Utils (but am open to pure advanced xml solutions as well). I have a problem where I have a multi-dropdown on one page, and want to drilldown into another page. This works fine when I have one selection and no quotes in the token. But when there is more than one selection, then I need to use a Pulldown template to build the OR string, which requires the token to contain equals sign(s) (Example: $application$ template value may be...  application=value1 OR application=value2). Also, I need to put quotes around the $value$ token in order to account for spaces in the values. Both the equal signs and quotes are getting encoded in the URL string (equals is changed to %3D and quote to %22) and the page I am drilling into does not capture the values correctly.&lt;/P&gt;

&lt;P&gt;Is there some way to overcome this so that the tokens can get passed along with = and " inside the value and the target page reads them correctly?&lt;/P&gt;</description>
    <pubDate>Thu, 29 May 2014 20:23:49 GMT</pubDate>
    <dc:creator>jamesvz84</dc:creator>
    <dc:date>2014-05-29T20:23:49Z</dc:date>
    <item>
      <title>Drilldown - Passing along equals (=) and quotes (") in parameter values</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183098#M11286</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am using SideView Utils (but am open to pure advanced xml solutions as well). I have a problem where I have a multi-dropdown on one page, and want to drilldown into another page. This works fine when I have one selection and no quotes in the token. But when there is more than one selection, then I need to use a Pulldown template to build the OR string, which requires the token to contain equals sign(s) (Example: $application$ template value may be...  application=value1 OR application=value2). Also, I need to put quotes around the $value$ token in order to account for spaces in the values. Both the equal signs and quotes are getting encoded in the URL string (equals is changed to %3D and quote to %22) and the page I am drilling into does not capture the values correctly.&lt;/P&gt;

&lt;P&gt;Is there some way to overcome this so that the tokens can get passed along with = and " inside the value and the target page reads them correctly?&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 20:23:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183098#M11286</guid>
      <dc:creator>jamesvz84</dc:creator>
      <dc:date>2014-05-29T20:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown - Passing along equals (=) and quotes (") in parameter values</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183099#M11287</link>
      <description>&lt;P&gt;How about replacing the values at target page for "%3D" with = and %22 with space before using them?&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 20:44:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183099#M11287</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-05-29T20:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown - Passing along equals (=) and quotes (") in parameter values</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183100#M11288</link>
      <description>&lt;P&gt;The problem I see is performing the replacement before my search string needs it. I'd rather not use eval + search to do this, because first I'd have to pipe a large dataset then replace the characters in the values then actually search for the updated values. Unless there is another way to do this that I am not thinking of...&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 21:07:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183100#M11288</guid>
      <dc:creator>jamesvz84</dc:creator>
      <dc:date>2014-05-29T21:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown - Passing along equals (=) and quotes (") in parameter values</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183101#M11289</link>
      <description>&lt;P&gt;Disregard,&lt;/P&gt;

&lt;P&gt;Upon inspection of the search, there was another issue in the query. The characters = and " actually DID decode automatically.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2014 21:25:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183101#M11289</guid>
      <dc:creator>jamesvz84</dc:creator>
      <dc:date>2014-05-29T21:25:46Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown - Passing along equals (=) and quotes (") in parameter values</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183102#M11290</link>
      <description>&lt;P&gt;One high level piece of advice - is that whenever you're passing values in querystring args,  it is recommended to always use the &lt;CODE&gt;foo.rawValue&lt;/CODE&gt; tokens rather than the &lt;CODE&gt;$foo$&lt;/CODE&gt; token itself.  This  convention takes a little getting used to, but it's a very good thing in the long run. &lt;/P&gt;

&lt;P&gt;Granted,  if you're just plugging it into the search language ont the target page and doing nothing else with it, what you're doing is exactly right.&lt;/P&gt;

&lt;P&gt;Also if you need to reconstitute the raw array-valued token back into a search expression on the target page, the ArrayValueSetter module can do that for you.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jun 2014 22:47:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Drilldown-Passing-along-equals-and-quotes-quot-in-parameter/m-p/183102#M11290</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2014-06-02T22:47:57Z</dc:date>
    </item>
  </channel>
</rss>

