Loading...
 
Features / Usability

Features / Usability


Tracker csv import errors in v2.0

posts: 838 United Kingdom

Just upgraded a site from 1.9.11 to 2.0 and I'm still checking out that everything works the same, and I've got stuck with importing csv files to Trackers. The site has a number of existing Trackers that all seem to work OK but when I tried the csv import of some test data I got the error msg "Duplicate header names".

Thinking I had just screwed up something I exported all the existing data with all the fields and simply tried to reimport this file - but got the same error message. Have tried several more things to see if I could figure out what is happening, including duplicating the existing Tracker - but I keep getting this same error.

Can anyone tell me what the error message actually means and what I could be doing wrong.

Thanks

Geoff

posts: 7

I saw that same error before. I worked around it by removing the first row out of the csv file, you know the header row. That worked for me.


darreln


posts: 838 United Kingdom

Thanks but it is still not working even when I do that.

Its very odd I've got 8 separate trackers that all work in my 1.9.11 instance and I can import/export from them fine. In my 2.0 version of the same data I've now checked and 7 of them are fine on import and export ie I can export all their data and then reimport the same file after cutting it down just for test purposes and deleting the itemID values. But with the 8th Tracker I just keep getting this error no matter what I do. I'm going to rebuild the dataset from scratch in the 2.0 instance and see if that makes any difference.

If anyone else has any ideas I'd really appreciate it

Thanks

geoff


posts: 838 United Kingdom

OK so perhaps it is obvious in retrospect redface but "Duplicate header names" simply seems to mean more than one Tracker Field Name has exactly the same description (might be good to change that error message to Duplicated Field Name sometime?). I'm assuming that in 1.9.11 I 'got away' with this slightly sloppy way of working where from the actual context I was using, it was quite clear what was what, and the individual FieldID was obviously unique in each case. But I'm guessing v2.0 is now doing some extra checks when importing data and stops the process with this error message if it finds two Field Names with the same text description irrespective of their FieldID.

So all I did was edit the offending Field Name text and it all works fine biggrin