Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Trying to import work item updates, but get the error for all rows: The CSV File is missing a proper identifier ... I have the column Id which corresponds to valid records, so Why?

Trying to import work item updates, but get the error for all rows: The CSV File is missing a proper identifier ... I have the column Id which corresponds to valid records, so Why?

Sample:
"Id","Acceptance Test","Comments","Description","Resolution"
"34831","","1. Thomas, Donna (Dell) - 5/9/13 8:37 AM test","Training Task.",""

In that example, Id 34831 exists and is editable. I have JazzAdmin group and all permissions in project area.

Any help is greatly appreciated and urgent.

1 vote

Comments

BTW - using 4.0.5.

usually this happens to me when I say comma separated and its Tab or vice versa 

I've been using only comma separated for the first 15-20 attempts - all the time confirming the delimiter. Then I started trying to change the delimiter. But I am indicating the difference in the import dialog box.

Also FYI - I've removed the Comments field, the quotes, tried tab and semi-colon delimiters, and many permutations of ID (like: ID, Id, id, iD... with quotes, without quotes, etc.)

also, did u edit the file at al?  try opening with notepad++ or some editor where u can see the char encoding. I ran into a problem where the encoding was ANSI-UTF8, and the importer couldn't handle it.  I had to explicitly change it to UTF8.. then the importer worked.

excel leaves the file in weird state

Good idea - thought of the encoding too. I've never had a problem in the past. I double checked with Notepad ++ and it says it is encoded as UTF-8. I'll try resetting the encoding...

UTF-8 and still doesn't work.

showing 5 of 7 show 2 more comments


One answer

Permanent link
Line Feed – not CRLF – just LF. In Notepad it looks like a type-o… but in Notepad ++ it looks normal… so I finally turned on Notepad++ feature to show all hidden characters… and I realized – they didn’t all say CRLF… some were just LF. 

That is in the Comment field – not in the other fields. I got the other fields to work after I removed the Comment field from the import.

So – for the comment field – I found that the last record's comment exported (out of RTC 4.0.5) put in a non-printing character outside the quotes but before the end of line. I found that by removing the CRLFs from the comment field.

NO - I did not test it further to see if removing that non-printing character would fix the import of comments altogether. I was just happy I could get it to work.

1 vote

Comments

great that you found a solution!..

I also had to use tab delimiter when I had multi-row contents on the import (comments, description, acceptance criteria))

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 173

Question asked: Mar 17 '14, 5:15 p.m.

Question was seen: 11,589 times

Last updated: Mar 18 '14, 6:14 a.m.

Confirmation Cancel Confirm