CSV round trip not successful
2 answers
Export module to CSV:
Create a view with columns (and filters if needed) in the module and save. Click on pencil icon of saved view and select “Export…”.
Makes changes as needed in CSV. You can get rid of the meta data at the bottom. You can get rid of the “isHeading”, “parentBinding”, “module” columns assuming you’re not modifying the module structure. But don’t delete or modify the “id” or “Artifact Type” values! (Unless you’re adding rows in which case leave “id” blank and set an “Artifact Type”.)
Import CSV into module:
Select menu option “Artifacts > Import Artifact…”.
Select “Import requirements from a CSV file”, press “Next >”.
Choose your CSV file with “Choose File” button.
Choose “Import requirements into a module” and select the module with “Pick Module…” button.
(That part really only matters for NEW artifacts!)
If all you’re doing is modifying existing artifacts, choose the bottom option “Update artifacts that match entries, and ignore new entries”. If you created new rows in the CSV, choose the one above it. The top one will create all new entries.
Press “Finish” button.
Comments
Thanks M.K for the detailed response. Unfortunately I am not able to see the options at the bottom sometimes. It directly displays the FInish button after i pick the module. Any idea why this is happening?
No idea. Maybe put a screen shot on the web somewhere and link it?
I can confirm the behavior Iakshmi is reporting. I am running a 6.0.1 DOORS NG application and the CSV import dialog does not have options labeled "Update artifacts that match entries, and ignore new entries". No such option exists.
In my experience, you definitely have to retain all of the columns that get exported, such as Artifact Type, isHeading, parentBinding, and moduleId. You do not need the metadata info at the bottom of the export.
My effort was to fill in a custom attribute (pre-created in DNG) from an external .csv
I am at 6.0.1
Changes coming in 6.0.3 for migration and round tripping