<?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: Why does Email Report change column order? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470116#M80848</link>
    <description>&lt;P&gt;I was not, my order was being derived from:&lt;/P&gt;

&lt;P&gt;|stats count as #Trans by DeptName App Region Tran USERID EmpName ACF2Name _time&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jun 2020 17:12:24 GMT</pubDate>
    <dc:creator>njones781</dc:creator>
    <dc:date>2020-06-02T17:12:24Z</dc:date>
    <item>
      <title>Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470114#M80846</link>
      <description>&lt;P&gt;_Time is the column that gets moved from last to first only within the reports csv. Within the Inline results, the search, and a direct csv from the search keeps the columns in the correct order. How can I correct for this current and future reports?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 00:03:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470114#M80846</guid>
      <dc:creator>njones781</dc:creator>
      <dc:date>2020-06-07T00:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470115#M80847</link>
      <description>&lt;P&gt;Are you using a &lt;CODE&gt;table&lt;/CODE&gt; command to set the field order?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 17:06:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470115#M80847</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-02T17:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470116#M80848</link>
      <description>&lt;P&gt;I was not, my order was being derived from:&lt;/P&gt;

&lt;P&gt;|stats count as #Trans by DeptName App Region Tran USERID EmpName ACF2Name _time&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 17:12:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470116#M80848</guid>
      <dc:creator>njones781</dc:creator>
      <dc:date>2020-06-02T17:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470117#M80849</link>
      <description>&lt;P&gt;Use a &lt;CODE&gt;table&lt;/CODE&gt; command to specify the order in which to display fields.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 17:18:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470117#M80849</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-02T17:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470118#M80850</link>
      <description>&lt;P&gt;|table DeptName App Region Tran USERID EmpName ACF2Name _time&lt;/P&gt;

&lt;P&gt;Adding in this additional line did not have an impact on the Report csv column order.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 18:13:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470118#M80850</guid>
      <dc:creator>njones781</dc:creator>
      <dc:date>2020-06-02T18:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470119#M80851</link>
      <description>&lt;P&gt;You may need to submit a support request.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 12:38:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/470119#M80851</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-03T12:38:07Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Email Report change column order?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/519047#M87798</link>
      <description>&lt;P&gt;It appears that Splunk detects the "_time" fields and makes a decision that this should be first - I assume as _time is the only true law in the universe. So if you rename the field to a custom name like "timefield" - is it no longer considered a special case and will now follow the order specified by the fields or table command.&lt;/P&gt;&lt;P&gt;Another consideration is that when a field is called "_time" and contains an epoch time value - Splunk will automatically convert it to a readable format. However when you rename to something else, Splunk will just show the epoch value. So you also need to add a eval with strftime to convert the value to your preferred readable time.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 11:38:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Email-Report-change-column-order/m-p/519047#M87798</guid>
      <dc:creator>wyfwa4</dc:creator>
      <dc:date>2020-09-11T11:38:12Z</dc:date>
    </item>
  </channel>
</rss>

