Error importing CSV

I agree: the error message needs to be more specific.
Here are my suggestions for fixing a CSV import into the RM application.

Re-read the on-line information center pages on CSV import and ensure you have the all the required fields.

Search the RRC forum on jazz.net for past discussions.

Make sure the artifact types and associated attributes are already define in the RRC project type system you are importing into

Make sure the headings in the CSV file match what's in the names of attributes; it's a good idea to export a CSV file from RRC and use that header (you may need to add any missing columns that are required during import)

Make sure you don't use any special characters in your artifact or attribute names. This include - / ? " ' & ( ) and maybe others

Make sure you are properly "escaping" any quotation marks in the middle of the text you are trying to import; they have a special meaning in CSV files.

If you can't get it to work after that, start with a two-line CSV file: header + one row with data to import. Get that working, then add additional rows and additional attribute types.

Best wishes.

I figured out that the reason was because I had extra columns for some other parameters I wanted to include for each artifact. Is there a way to import data on more than just the 4 primary (Type, Title, Primary Text, Description?)?

Another attempt was to try and create a sample custom artifact, then export it so I would get the template. Immediately importing the exact same .csv yielded the same errors. Ideas?

I figured out that the reason was because I had extra columns for some other parameters I wanted to include for each artifact. Is there a way to import data on more than just the 4 primary (Type, Title, Primary Text, Description?)?

Yes you can include other columns. Each one becomes an attribute for the artifact. The header name is the attribute name as defined in RRC. It must be pre-defined and be a reasonable type for the data you are importing (ie. you probably can't import textual characters into an attributed defined as a number).

Another attempt was to try and create a sample custom artifact, then export it so I would get the template. Immediately importing the exact same .csv yielded the same errors. Ideas?

I suggest reviewing the list of suggestions I posted earlier and trying again. An exported CSV file may not include all columns necessary for importing (e.g. artifact type). The columns in the export are governed by the current columns visible in the RRC UI (or the RRC saved filter, if you are exporting right from the saved filter).

I figured out that the reason was because I had extra columns for some other parameters I wanted to include for each artifact. Is there a way to import data on more than just the 4 primary (Type, Title, Primary Text, Description?)?

Yes you can include other columns. Each one becomes an attribute for the artifact. The header name is the attribute name as defined in RRC. It must be pre-defined and be a reasonable type for the data you are importing (ie. you probably can't import textual characters into an attributed defined as a number).

Another attempt was to try and create a sample custom artifact, then export it so I would get the template. Immediately importing the exact same .csv yielded the same errors. Ideas?

I suggest reviewing the list of suggestions I posted earlier and trying again. An exported CSV file may not include all columns necessary for importing (e.g. artifact type). The columns in the export are governed by the current columns visible in the RRC UI (or the RRC saved filter, if you are exporting right from the saved filter).

Thanks Daniel, that was a big help! It seems my error was happening when I had a poorly defined header, and the importer didn't know where to put the information. Will have to be very careful defining my headers so they line up with my Attribute names in the future.