0.84.3 csv export is not formatted correctly

linker3000 · 2013-12-18 14:06:50

Hi,

I was wondering why the results of a ticket search saved in csv format was not importing properly into Excel so I opened the file in Notepad++ and here's the header line:

"ID;""";"Title""Entity"";""Status"";""Solution type"";""Opening date"";""Last update"";""Last updater"";""Priority"";""Requester"";""Technician"";""Technician group"";""Category"";""Due date"";""Due date + Progress"";""Closing time"";""Waiting time"";""Number of followups"";""Number of all linked tickets"";"

This is really crazy! There's extra quotes and semicolons inside quotes - No wonder Excel had such a hard time!!

SYLK format nearly works - but after opening a saved file here's a couple of Excel columns:

ID
2 ;951 [Should be ticket 2951 etc...]
2 ;918
2 ;916
2 ;826
2 ;822
2 ;823
2 ;824
2 ;821
2 ;820
2 ;819
2 ;818
2 ;817
2 ;813
2 ;812
2 ;737
2 ;715

Status
;Pending
;New
;Closed
;Closed
;Closed
;Closed
;Closed
;Closed
;Closed
;Closed
;Closed
;Closed
;Solved
;New
;Closed
;New

Any comments before I consider a bug report?

Thanks

Last edited by linker3000 (2013-12-18 14:22:39)

danh · 2014-01-11 19:05:05

I agree, this seems to be a bug to me.

MoYo · 2014-01-12 01:09:40

move to investigate

MoYo · 2014-01-12 12:36:54

but could not reproduce.

linker3000 · 2014-01-13 12:24:34

MoYo wrote:

but could not reproduce.

Agreed - I have just tried three more exports and they all worked OK. EDIT: See below.

Since the original report, GLPI has been moved onto a different server (VM) by exporting/importing the database and copying the Web folder so this might be related to other code or library versions, but I don't propose to do any checking as it seems to be an isolated incident. Both servers are CentOS release 6.4 (Final) 64-bit.

Last edited by linker3000 (2014-01-16 16:23:35)

linker3000 · 2014-01-16 16:24:50

EDIT: 16th Jan 2014

I originally edited my earlier reply with this info but decided it would be better put as a new forum post...

Actually, there are still some minor issues with the CSV export - for example, if a ticket has an SLA value, the output line is broken around the SLA end date/percentage complete value:

"ID";"Title";"Entity";"Status";"Solution type";"Opening date";"Last update";"Last updater";"Priority";"Requester";"Technician";"Technician group";"Category";"Due date";"Due date + Progress";"Closing time";"Waiting time";"Number of followups";"Number of all linked tickets";
"3 240";"Check message";"Root entity";"Processing (assigned)";"";"13-01-2014 22:44";"14-01-2014 08:52";"James Smith";"Medium";"customer@example.com";"James Sillman";"";"OurCompany";"14-01-2014 11:15";"14-01-2014

84%";"0 seconds";"0 seconds";"0";"0";

There are two (hex) 0a codes between '2014' and '84%'

There are also extra new lines if a ticket has multiple people assigned to it:

"3 161";"Tracking for ongoing investigation into server BSOD/Spurious reboots";"Root entity";"Processing (assigned)";"";"02-01-2014 15:28";"13-01-2014 14:13";"MY Name";"High";"customer@example.com";"My name [LINE BREAK HERE]
Second name";"Service Desk Team";"Customer A > Site";"--";"";"0 seconds";"0 seconds";"12";"0";

The hex codes between the two names are 20 0a (space and line feed)

These are reasonably cosmetic and can be fixed, but they do mean that some work is needed when a text export is brought into a spreadsheet (eg: Excel) via a csv import

Forum GLPI-Project

Announcement

#1 2013-12-18 14:06:50

0.84.3 csv export is not formatted correctly

#2 2014-01-11 19:05:05

Re: 0.84.3 csv export is not formatted correctly

#3 2014-01-12 01:09:40

Re: 0.84.3 csv export is not formatted correctly

#4 2014-01-12 12:36:54

Re: 0.84.3 csv export is not formatted correctly

#5 2014-01-13 12:24:34

Re: 0.84.3 csv export is not formatted correctly

#6 2014-01-16 16:24:50

Re: 0.84.3 csv export is not formatted correctly

Board footer