<?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: Token for a field containing spaces and special characters in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/755578#M59272</link>
    <description>&lt;P&gt;&lt;STRONG&gt;This is old, but in case anyone comes here looking for an answer... for tokens used in email or other alert actions (e.g. ServiceNow INC creation), in Splunk 9.4+ it simply works when using field names with spaces.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;So if you have a fieldname with spaces, produced from a search with something like:&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| table Queue "Message Count"&lt;/LI-CODE&gt;&lt;P&gt;Then you can include that field in the alert/SNow action with:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$result.Message Count$&lt;/LI-CODE&gt;</description>
    <pubDate>Mon, 17 Nov 2025 12:53:12 GMT</pubDate>
    <dc:creator>gsinclair-lc</dc:creator>
    <dc:date>2025-11-17T12:53:12Z</dc:date>
    <item>
      <title>Token for a field containing spaces and special characters</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343217#M22321</link>
      <description>&lt;P&gt;How do I return the value of a field that contains spaces and special characters using a Token? The field name is License quota used (%) &lt;/P&gt;

&lt;P&gt;I tried the following combinations, however none appear to work.&lt;/P&gt;

&lt;P&gt;$result."License quota used (%)"$&lt;BR /&gt;
$"result.License quota used (%)"$&lt;BR /&gt;
$result.License quota used (%)$"&lt;/P&gt;

&lt;P&gt;Tried single quotes as well, but no luck.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2017 12:05:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343217#M22321</guid>
      <dc:creator>chintu_jain</dc:creator>
      <dc:date>2017-09-20T12:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Token for a field containing spaces and special characters</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343218#M22322</link>
      <description>&lt;P&gt;Try this&lt;/P&gt;

&lt;P&gt;1) $result.License%20quota%20used%20(%)$&lt;/P&gt;

&lt;P&gt;or&lt;/P&gt;

&lt;P&gt;2) &amp;lt;eval token="licenselabel"&amp;gt;License quota used (%)&amp;lt;/eval&amp;gt;&lt;BR /&gt;
     $result.licenselabel$&lt;BR /&gt;
or&lt;/P&gt;

&lt;P&gt;3) "$result.'License quota used (%)$"&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2017 14:51:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343218#M22322</guid>
      <dc:creator>sbbadri</dc:creator>
      <dc:date>2017-09-20T14:51:40Z</dc:date>
    </item>
    <item>
      <title>Re: Token for a field containing spaces and special characters</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343219#M22323</link>
      <description>&lt;P&gt;The token and the label don't have to be the same. Why not make the token easy to use?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2017 15:31:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343219#M22323</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-09-20T15:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: Token for a field containing spaces and special characters</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343220#M22324</link>
      <description>&lt;P&gt;I am trying to do similar things in sending email alert, with inline table included. Point 1 and 3 did not work&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2018 01:59:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/343220#M22324</guid>
      <dc:creator>chanmi2</dc:creator>
      <dc:date>2018-05-11T01:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: Token for a field containing spaces and special characters</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/755578#M59272</link>
      <description>&lt;P&gt;&lt;STRONG&gt;This is old, but in case anyone comes here looking for an answer... for tokens used in email or other alert actions (e.g. ServiceNow INC creation), in Splunk 9.4+ it simply works when using field names with spaces.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;So if you have a fieldname with spaces, produced from a search with something like:&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| table Queue "Message Count"&lt;/LI-CODE&gt;&lt;P&gt;Then you can include that field in the alert/SNow action with:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$result.Message Count$&lt;/LI-CODE&gt;</description>
      <pubDate>Mon, 17 Nov 2025 12:53:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Token-for-a-field-containing-spaces-and-special-characters/m-p/755578#M59272</guid>
      <dc:creator>gsinclair-lc</dc:creator>
      <dc:date>2025-11-17T12:53:12Z</dc:date>
    </item>
  </channel>
</rss>

