<?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 Splunk 6 data model restrictions based on attribute type in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121898#M2709</link>
    <description>&lt;P&gt;I've started playing around with Splunk 6, looking at data models and pivot tables. In my data model, I have a child object that contains numeric attributes, with a root object representing a user. The child object represents repetitive events, e.g. "Profile saved" events, that might contain values like "how many times a day do you brush your teeth" and "how much do you spend on toothpaste" (for illustrative purposes).&lt;/P&gt;

&lt;P&gt;If I configure the object with these attributes as "Numeric", and want to use the last value (to get the most recent amount that a user spends on toothpaste), I am unable to do so, because the "Values" drop-down in the Column Values section doesn't include "last" value - last, first and list are available for strings, while numeric only offers mathematical functions (sum, etc).&lt;/P&gt;

&lt;P&gt;Is there a way to reconfigure Splunk6 to allow "last" function on numeric values (assuming that in the background, the pivot is using a stats function for this).&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2013 11:43:58 GMT</pubDate>
    <dc:creator>brettcave</dc:creator>
    <dc:date>2013-10-30T11:43:58Z</dc:date>
    <item>
      <title>Splunk 6 data model restrictions based on attribute type</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121898#M2709</link>
      <description>&lt;P&gt;I've started playing around with Splunk 6, looking at data models and pivot tables. In my data model, I have a child object that contains numeric attributes, with a root object representing a user. The child object represents repetitive events, e.g. "Profile saved" events, that might contain values like "how many times a day do you brush your teeth" and "how much do you spend on toothpaste" (for illustrative purposes).&lt;/P&gt;

&lt;P&gt;If I configure the object with these attributes as "Numeric", and want to use the last value (to get the most recent amount that a user spends on toothpaste), I am unable to do so, because the "Values" drop-down in the Column Values section doesn't include "last" value - last, first and list are available for strings, while numeric only offers mathematical functions (sum, etc).&lt;/P&gt;

&lt;P&gt;Is there a way to reconfigure Splunk6 to allow "last" function on numeric values (assuming that in the background, the pivot is using a stats function for this).&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2013 11:43:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121898#M2709</guid>
      <dc:creator>brettcave</dc:creator>
      <dc:date>2013-10-30T11:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 6 data model restrictions based on attribute type</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121899#M2710</link>
      <description>&lt;P&gt;Unfortunately the contents of the "Values" drop-down is not configurable at the moment, though it's likely we will be adding more options for each data type in future releases.&lt;/P&gt;

&lt;P&gt;In the meantime, one workaround you can try is to create a new Eval attribute that you just set equal to the original numeric attribute, but make the new attribute a string.  Then in pivot you should be able do numeric operations on one and string operations on the other.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2013 19:14:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121899#M2710</guid>
      <dc:creator>Simon_Fishel</dc:creator>
      <dc:date>2013-10-30T19:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 6 data model restrictions based on attribute type</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121900#M2711</link>
      <description>&lt;P&gt;Thanks Simon. I did try the workaround. The only problem is when you try report (graphically) on a string - you can't represent the value (numerically).&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2013 07:47:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121900#M2711</guid>
      <dc:creator>brettcave</dc:creator>
      <dc:date>2013-10-31T07:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 6 data model restrictions based on attribute type</title>
      <link>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121901#M2712</link>
      <description>&lt;P&gt;In what way can't you represent it numerically?  Do you mean you'd like to make it the y-axis of a chart?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2013 14:06:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Splunk-6-data-model-restrictions-based-on-attribute-type/m-p/121901#M2712</guid>
      <dc:creator>Simon_Fishel</dc:creator>
      <dc:date>2013-10-31T14:06:09Z</dc:date>
    </item>
  </channel>
</rss>

