Without a sample of what is wrong, or a better description of the bug,
I have to assume that the original reporter either wants to come up to
3.8.8 or apply 1f4fa271b9e9c78104257f729f3046f9c30694e0 which fixes a
bug where the column headers and column bodies might not be in sync.
-kevin
Thanks
Jeff, et all,
I think it has been doing this for years. I just remember to change the Data
Type to ".xls" and all is well.
Kenn
LBNL
On Wed, Nov 3, 2010 at 1:16 PM, Kevin Falcone wrote:
> On Wed, Nov 03, 2010 at 01:05:25PM -0700, Tom Lahti wrote:
> > > Using OO 3.2
> > >(*) Separated by
> >
On Wed, Nov 03, 2010 at 01:05:25PM -0700, Tom Lahti wrote:
> > Using OO 3.2
> >(*) Separated by
> >
> >[x] Tab [ ] Comma
> >[ ] Semicolon [ ] Space
> >
> > = broken :(
> >
> > I'll ask the original problem finder what app she was using.
>
> Does the data contain em
> Using OO 3.2
>(*) Separated by
>
>[x] Tab [ ] Comma
>[ ] Semicolon [ ] Space
>
> = broken :(
>
> I'll ask the original problem finder what app she was using.
Does the data contain embedded tabs? If so, tab-delimited ain't gonna work.
Is she sure she did TAB sep
On 11/3/2010 1:59 PM, Jesse Vincent wrote:
On Wed 3.Nov'10 at 10:45:54 -0400, Jeff Blaine wrote:
The "Spreadsheet" link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.
That's not something I've he
On Wed 3.Nov'10 at 10:45:54 -0400, Jeff Blaine wrote:
> The "Spreadsheet" link exports TSV which completely botches
> the data values associated with our custom fields. The
> Custom Field data appears in all the wrong columns.
That's not something I've heard reported. I do know we improved th
On Wed, Nov 03, 2010 at 10:45:54AM -0400, Jeff Blaine wrote:
> The "Spreadsheet" link exports TSV which completely botches
> the data values associated with our custom fields. The
> Custom Field data appears in all the wrong columns.
>
You may use as an alternative the extension
RT::Extension::S
The "Spreadsheet" link exports TSV which completely botches
the data values associated with our custom fields. The
Custom Field data appears in all the wrong columns.
Is this a known bug?
