<?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: appendcols not working aligning values correctly in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633178#M219948</link>
    <description>&lt;P&gt;It DOES work beautifully! Thank you so much! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;I learned something new in Splunk today. The explanation helped a lot.&lt;/P&gt;</description>
    <pubDate>Fri, 03 Mar 2023 14:14:40 GMT</pubDate>
    <dc:creator>Dyana_a</dc:creator>
    <dc:date>2023-03-03T14:14:40Z</dc:date>
    <item>
      <title>Why is appendcols not working aligning values correctly?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633078#M219913</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;I'd like to know if someone can help me with this:&lt;/P&gt;
&lt;P&gt;I have 4 saved searches that gives back counts for WTD (Week-to-Date), MTD (Month), QTD (quarter) and YTD (year) per type and a dashboard that calls those 4 searches that would display as columns per branch:&lt;/P&gt;
&lt;P&gt;Example:&lt;BR /&gt;&lt;BR /&gt;Branch dropdown: Avenue1&amp;nbsp; &amp;lt;--- the dashboard will have this and the numbers will change accordingly.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; WTD&amp;nbsp; &amp;nbsp; MTD&amp;nbsp; &amp;nbsp;QTD&amp;nbsp; &amp;nbsp; YTD&lt;BR /&gt;PROD type 1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;4&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;85&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;85&lt;BR /&gt;PROD type 3&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp;1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;1&lt;BR /&gt;PROD type 40&amp;nbsp; &amp;nbsp; &amp;nbsp;1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp;6&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;6&lt;/P&gt;
&lt;P&gt;...&lt;BR /&gt;Total&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;5&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 92&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;92&lt;BR /&gt;&lt;BR /&gt;The Dashboard will have the following( I hardcoded the branch for now):&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;| loadjob savedsearch="....:search:Retail_TEST_QTD"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| rename CREATEDATBRANCH as Branch&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| lookup BranchNums Branch &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| search BranchNames="Avenue1"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count(TOTALCOUNT) as QTD by DESCRIPTION&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| appendcols&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;[| loadjob savedsearch="....:search:Retail_TEST_YTD"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| rename CREATEDATBRANCH as Branch&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| lookup BranchNums Branch &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| search BranchNames="Avenue1"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count(TOTALCOUNT) as YTD by DESCRIPTION]&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| appendcols&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;[| loadjob savedsearch="....:search:Retail_TEST_MTD"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| rename CREATEDATBRANCH as Branch&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| lookup BranchNums Branch &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| search BranchNames="Avenue1"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count(TOTALCOUNT) as MTD by DESCRIPTION]&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| appendcols&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;[| loadjob savedsearch="....:search:Retail_TEST_WTD"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| rename CREATEDATBRANCH as Branch&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| lookup BranchNums Branch &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| search BranchNames="Avenue1"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count(TOTALCOUNT) as WTD by DESCRIPTION]&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| rename DESCRIPTION as PROD_DESCRIPTION&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;| table PROD_DESCRIPTION WTD MTD QTD YTD&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| addtotals row=f col=t labelfield=PROD_DESCRIPTION label="PROD Total:"&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;and these are the saved searches.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Saved search title:&amp;nbsp; Retail_TEST_WTD&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;index=.... host=.... source=.... sourcetype=.... NOT CLOSEDATE=* AND &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;(TYPE = 1 OR TYPE = 2 OR TYPE = 3 OR TYPE = 4 OR TYPE = 5 OR TYPE = 6 OR &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE = 8 OR TYPE = 9 OR TYPE = 15 OR TYPE = 40 OR TYPE = 61 OR TYPE = 63)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| dedup PARENTACCOUNT ID &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| eventstats count as TOTALCOUNT by TYPE, CREATEDATBRANCH&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| eval OPENDATE=strptime(OPENDATE,"%Y-%m-%d %H:%M:%S.%Q")&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| eval RANGE = "-1@w"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| where OPENDATE &amp;gt;= (relative_time(now(),RANGE)) &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| eval DESCRIPTION = case(TYPE=1, "PROD Type 1",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=2, "PROD Type 2",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=3, "PROD Type 3",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=4, "PROD Type 4",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=5, "PROD Type 5",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=6, "PROD Type 6",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=8, "PROD Type 8",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=9, "PROD Type 9",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=15, "PROD Type 15",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=40, "PROD Type 40",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=61, "PROD Type 61",&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TYPE=63, "PROD Type 63")&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Saved search title: Retail_TEST_MTD&lt;BR /&gt;| eval RANGE = "-1@mon"&amp;nbsp; &amp;nbsp; &amp;lt;--- same as above but with this change&lt;/P&gt;
&lt;P&gt;Saved search title: Retail_TEST_QTD&lt;BR /&gt;| eval RANGE = "-1@qtr"&lt;/P&gt;
&lt;P&gt;Saved search title: Retail_TEST_YTD&lt;BR /&gt;| eval RANGE = "-1@y"&lt;BR /&gt;&lt;BR /&gt;The misplacement of the counts occurs only in the WTD column, which should be the following:&lt;BR /&gt;&lt;BR /&gt;for Prod Type 40 should be 1 count for Avenue1&lt;BR /&gt;Weekly (correct counts):&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dyana_a_0-1677797803232.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24158i8E5BA38A9AB1E1AB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Dyana_a_0-1677797803232.png" alt="Dyana_a_0-1677797803232.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Dyana_a_0-1677797803232.png&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;Quarter (correct counts):&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dyana_a_3-1677798509206.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24161i268D2F651E21F4BB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Dyana_a_3-1677798509206.png" alt="Dyana_a_3-1677798509206.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Dyana_a_3-1677798509206.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;But I am getting this: the 1 count that belongs in Prod Type 40 is showing in Prod 3 instead for the WTD:&lt;BR /&gt;All other columns MTD, QTD, and YTD numbers match fine&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dyana_a_2-1677798012406.png" style="width: 496px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24160i3FFCF470DA0FCA11/image-dimensions/496x153?v=v2" width="496" height="153" role="button" title="Dyana_a_2-1677798012406.png" alt="Dyana_a_2-1677798012406.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Dyana_a_2-1677798012406.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Note: the discrepancy in Prod Type 1 for the QTD and YTD is okay because Splunk is not up to date, it's 2 days behind.&lt;/P&gt;
&lt;P&gt;If anyone please , can tell me what I am doing wrong. I have cloned each of the saved searches. And I made sure the DESCRIPTION are all the same across all saves searches.&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Dyana&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 16:38:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633078#M219913</guid>
      <dc:creator>Dyana_a</dc:creator>
      <dc:date>2023-03-03T16:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols not working aligning values correctly</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633088#M219918</link>
      <description>&lt;P&gt;This is a well-explained post, nicely done.&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;What's Wrong?&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;The issue here is that the | appendcols command does not respect any field values, it simply merges the events (rows) in the same order that the searches produce them in, read more &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Appendcols" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Step-by-step in context:&lt;/P&gt;&lt;P&gt;Say QTD_Search returns:&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;DESCRIPTION&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;QTD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;87&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="25px"&gt;3&lt;/TD&gt;&lt;TD height="25px"&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;40&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;6&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;BR /&gt;Say MTD_Search returns:&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;DESCRIPTION&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;MTD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%" height="25px"&gt;40&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;BR /&gt;Then,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;`QTD_Search`
| appendcols [`MTD_Search`]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Will essentially make a table like this:&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="25%" height="25px"&gt;DESCRIPTION&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;QTD&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;DESCRIPTION&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;MTD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="25%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;87&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="25%" height="25px"&gt;3&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;40&lt;/TD&gt;&lt;TD width="25%" height="25px"&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="25px"&gt;40&lt;/TD&gt;&lt;TD height="25px"&gt;6&lt;/TD&gt;&lt;TD height="25px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD height="25px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;BR /&gt;By default, the | appendcols command's override argument is set to false so when&amp;nbsp;when there is a field conflict (like DESCRIPTION) it basically gets dropped (which is masking your problem):&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;DESCRIPTION&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;QTD&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;MTD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;1&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;87&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="25px"&gt;3&lt;/TD&gt;&lt;TD height="25px"&gt;1&lt;/TD&gt;&lt;TD height="25px"&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;40&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;6&lt;/TD&gt;&lt;TD width="33.333333333333336%" height="25px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;BR /&gt;The reason why YTD is working must be because its DESCRIPTION lines up with QTD's throughout all of the rows.&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;How do we fix it?&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/U&gt;What you need, is something that will merge your result sets contextually based on the DESCRIPTION.&amp;nbsp; To address this we can use | append to append all of the subsearch results together at the bottom of the main search (retaining their PRODTYPE DESCRIPTIONS) and then a | stats command to organise them by DESCRIPTION at the end. Your new branch search might look something like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| loadjob savedsearch="....:search:Retail_TEST_QTD" 
| rename CREATEDATBRANCH as Branch 
| lookup BranchNums Branch 
| search BranchNames="Avenue1" 
| stats count(TOTALCOUNT) as QTD by DESCRIPTION 
| append 
    [| loadjob savedsearch="....:search:Retail_TEST_YTD" 
    | rename CREATEDATBRANCH as Branch 
    | lookup BranchNums Branch 
    | search BranchNames="Avenue1" 
    | stats count(TOTALCOUNT) as YTD by DESCRIPTION] 
| append 
    [| loadjob savedsearch="....:search:Retail_TEST_MTD" 
    | rename CREATEDATBRANCH as Branch 
    | lookup BranchNums Branch 
    | search BranchNames="Avenue1" 
    | stats count(TOTALCOUNT) as MTD by DESCRIPTION] 
| append 
    [| loadjob savedsearch="....:search:Retail_TEST_WTD" 
    | rename CREATEDATBRANCH as Branch 
    | lookup BranchNums Branch 
    | search BranchNames="Avenue1" 
    | stats count(TOTALCOUNT) as WTD by DESCRIPTION] 
| rename DESCRIPTION as PROD_DESCRIPTION 
| fields PROD_DESCRIPTION WTD MTD QTD YTD 
| stats values(*) as * by PROD_DESCRIPTION 
| table PROD_DESCRIPTION WTD MTD QTD YTD 
| addtotals row=f col=t labelfield=PROD_DESCRIPTION label="PROD Total:"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 13:03:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633088#M219918</guid>
      <dc:creator>Tom_Lundie</dc:creator>
      <dc:date>2023-03-03T13:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols not working aligning values correctly</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633167#M219944</link>
      <description>&lt;P&gt;Thank you TOM!&lt;/P&gt;&lt;P&gt;I will go ahead and test this now. I cannot wait to see if this will fix my problem. Thank you so much again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dyana&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 13:44:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633167#M219944</guid>
      <dc:creator>Dyana_a</dc:creator>
      <dc:date>2023-03-03T13:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols not working aligning values correctly</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633172#M219947</link>
      <description>&lt;P&gt;This is also a very detailed, well explained post! I understand what you're saying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dyana&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 13:51:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633172#M219947</guid>
      <dc:creator>Dyana_a</dc:creator>
      <dc:date>2023-03-03T13:51:15Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols not working aligning values correctly</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633178#M219948</link>
      <description>&lt;P&gt;It DOES work beautifully! Thank you so much! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;I learned something new in Splunk today. The explanation helped a lot.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 14:14:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633178#M219948</guid>
      <dc:creator>Dyana_a</dc:creator>
      <dc:date>2023-03-03T14:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols not working aligning values correctly</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633181#M219950</link>
      <description>&lt;P&gt;Great news, I'm glad this helped!&lt;/P&gt;&lt;P&gt;Feel free to mark this as the accepted solution, if you think it should be&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Mar 2023 14:23:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-is-appendcols-not-working-aligning-values-correctly/m-p/633181#M219950</guid>
      <dc:creator>Tom_Lundie</dc:creator>
      <dc:date>2023-03-03T14:23:37Z</dc:date>
    </item>
  </channel>
</rss>

