[rt-users] Spreadsheet/Export in 3.8.6/3.8.7 has column headers/data mixed up. Bug?

[Epp, Christopher CLBC:EX]

Yes, the new routines are faster. I'm happy with them. I was reporting the issue because I had seen someone asking about the same problem of having non-associated custom fields appear when they were not required. So in case the person saw the post they would see the answer. It would be nice to have had the release notes state that without installing Parse:BooleanLogic that there would be export issues.
 
Yes you are understanding correctly. The column data and column names did not match up for the custom fields. I believe I found the problem. In the Results.tsv file at line 110 the sort call had $a on both sides of the <=>. It was previously this:
 
    foreach my $name ( sort { $cf_name_to_pos{$a} <=> $cf_name_to_pos{$a} } keys %cf_name_to_pos ) {
 
I changed it to:
 
    foreach my $name ( sort { $cf_name_to_pos{$a} <=> $cf_name_to_pos{$b} } keys %cf_name_to_pos ) {
 
It now appears to work properly under any testing we have done. I am not a perl programmer, so I hope that was a correct fix.
 

________________________________

From: Ruslan Zakirov [mailto:ruslan.zakirov at gmail.com]
Sent: Mon 21/12/2009 1:56 PM
To: Epp, Christopher CLBC:EX
Cc: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Spreadsheet/Export in 3.8.6/3.8.7 has column headers/data mixed up. Bug?



On Fri, Dec 18, 2009 at 2:42 AM, Epp, Christopher CLBC:EX
<Christopher.Epp at gov.bc.ca> wrote:
> I upgraded 3.8.2 to both 3.8.6 and 3.8.7 in a test environment copied from my production installation.
>
> In both versions I have had problems with the spreadsheet function. At first, it changed output from the previous version by outputting all custom fields, even ones not related to the queue I was exporting. That was fixed when I installed the Parse::BooleanLogic cpan module.

But it's now 10 times faster, eats less memory, a stream instead of do
it all on the server and send data only when it's all done, so chances
to hit timeout are minimal.

> Now the problem is that the CF column headers are mixed up. So for example the CF-FirstName column heading would be over the LastName Data.

Hm. Do you mean that column name doesn't match data? Do I understand
it correctly?

>
> Is anyone else having this problem? Is this a bug?
>
> Cheers,
> Chris
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com <http://wiki.bestpractical.com/> 
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com <http://rtbook.bestpractical.com/> 
>



--
Best regards, Ruslan.