Errors occurred while the comma-separated values (CSV) file was being imported to the RRC 4.0.3
![]()
Can't figure out what's wrong with the import or the data in the import file. Note that the same CSV file has been imported successfully to the IBM sandbox 2.
Wonder if that has anything to do with importing requirements from a project on PROD, into a project on DEV , where the same access URI is used by tying the URL with the Dev server IP in the hosts file.
|
3 answers
![]()
This can't be marked as the right answer, as it is my own: However it is the right answer.
Sumitted [PMR 19291,49R,000], which is still opened:
That was what we found from IBM suggestions of a workaround, the PMR is still open, will update with any more to come.
|
![]()
By the look of it, the URL in the error message refers to an enumeration value. Is the URL the raw data in the CSV file? if so, it is not going to work on another system since the type system will be completely different. I would expect the literal value of the enumeration to appear in the CSV file.
Comments THat was what I thought, however there are no links on the requirements hence no link exported to the CSV file: Id, Name, Artifact Type, Last mod by, Last mod date
Besides the exact same CSV file got imported to the RRC on IBM sandbox 2 without a hitch. On second though, I think you might have a more serious problem with the system in question - the type system may be corrupted.
|
![]() Thanks Long, that horrible error message has cost me a few hours. Specifying defaults on multi enumerates not in the csv I'm tring to import solved it. Why can't it say something like, a default needs to be set for attribute type, not some gobbledygook? |
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.
Comments
Definitely it's the URL spoofing which caused issue: I exported requirements from a DEV project then reimported it back in under a different folder with name changes, got exactly same errors.