<?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: coloring a row based on field value(with a wildcard/space) in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90343#M23214</link>
    <description>&lt;P&gt;so a wildcard idea is not possible here?&lt;/P&gt;</description>
    <pubDate>Thu, 17 Jan 2013 10:43:07 GMT</pubDate>
    <dc:creator>smolcj</dc:creator>
    <dc:date>2013-01-17T10:43:07Z</dc:date>
    <item>
      <title>coloring a row based on field value(with a wildcard/space)</title>
      <link>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90341#M23212</link>
      <description>&lt;P&gt;hi,&lt;BR /&gt;
for changing the color of a field we can change the css to&lt;BR /&gt;
.Table tr.informational td {&lt;BR /&gt;
           background-color:#72c72d;&lt;BR /&gt;
              color:#fff;&lt;BR /&gt;
             }&lt;BR /&gt;
what if the field name is having some space or if we have to add a wild card in the field value like&lt;BR /&gt;
    .Table tr.informational 1 td {&lt;BR /&gt;
           background-color:#72c72d;&lt;BR /&gt;
              color:#fff;&lt;BR /&gt;
             }&lt;/P&gt;

&lt;P&gt;why i need wildcard because it can be  informational 2 informational 3... etc.. something like info*.. is it possible?&lt;BR /&gt;
Please help&lt;BR /&gt;
Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 06:46:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90341#M23212</guid>
      <dc:creator>smolcj</dc:creator>
      <dc:date>2013-01-17T06:46:39Z</dc:date>
    </item>
    <item>
      <title>Re: coloring a row based on field value(with a wildcard/space)</title>
      <link>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90342#M23213</link>
      <description>&lt;P&gt;In this question you're asking about the "rowClass" param of the Sideview Table module, and for those following along this question came from a comment on this other question - &lt;A href="http://splunk-base.splunk.com/answers/60993/colorize-simpleresultstable-rows-based-on-field-values" target="_blank"&gt;http://splunk-base.splunk.com/answers/60993/colorize-simpleresultstable-rows-based-on-field-values&lt;/A&gt;. &lt;/P&gt;

&lt;P&gt;The value of the Table module's rowClass param, as calculated at runtime can contain spaces, whether or not those spaces come from the dynamic field value(s) present by virtue of $fieldName$,  or from hardcoded parts of the string.  However in CSS a space in there means that multiple classes are being applied indepently to the element. EG: if the rowClass value were "informational 1",  then you'd be applying two classes independently, "informational",  and "1".  Each of those classes you'd have to define in your stylesheet, and needless to say "1" is a very strange classname to use.&lt;/P&gt;

&lt;P&gt;To simplify this, I would stay away from spaces in the fieldnames that you're using in rowClass.  Specifically I would use &lt;CODE&gt;| eval myClassField=replace(myClassField," ","_")&lt;/CODE&gt; either in the base search or in a postProcess search, to turn those values into "informational_1", "informational_2", etc..    That will mean they act as a single class and you can define those informational_1,  informational_2,  informational_3  in your CSS.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:07:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90342#M23213</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2020-09-28T13:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: coloring a row based on field value(with a wildcard/space)</title>
      <link>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90343#M23214</link>
      <description>&lt;P&gt;so a wildcard idea is not possible here?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 10:43:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90343#M23214</guid>
      <dc:creator>smolcj</dc:creator>
      <dc:date>2013-01-17T10:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: coloring a row based on field value(with a wildcard/space)</title>
      <link>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90344#M23215</link>
      <description>&lt;P&gt;No it is not.  No such mechanism exists in CSS and in fact the "&lt;EM&gt;" character has its own meaning in CSS that would confuse things even further.  Granted,  if you let the "informational 1" values come down as rowClass values,  you'd *get&lt;/EM&gt; your wildcard behavior in the form of the "informational" class.   You could leave the "1", "2" classes undefined and your "informational" class might work as the wild card you're wanting?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 18:10:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/coloring-a-row-based-on-field-value-with-a-wildcard-space/m-p/90344#M23215</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2013-01-17T18:10:50Z</dc:date>
    </item>
  </channel>
</rss>

