Importing and exporting CSV and spreadsheet files

You can import or export text-based artifacts to and from requirements projects by using comma-separated values (CSV) files or spreadsheets (XLS and XLSX) files. Round trip importing and exporting is also supported. For example, you can export artifacts to a CSV file, change the attribute values in the file, and then import that file back into IBM® Engineering Requirements Management DOORS® Next (DOORS Next).

Consider the following restrictions on the importing and exporting process:
  • Although the import is an asynchronous process, if you log out during the import process, you might encounter problems. For example, imported data might be truncated since the import process is not completed after you log out.
  • If you export a view that includes links, and then delete those links in the exported file, the links are not deleted when you import that file into the RM application.
  • You can create new tags for artifacts by importing a file, but if tags exist in the artifacts, they are ignored during the import process. You cannot delete tags from artifacts by importing a file.
  • You cannot export or import comments in requirement artifacts.
  • You can create text, heading type, module, collection, and diagrams when you import a CSV XLS, or XLSX file. When you import into a module, you can import text and diagrams only.
  • Rich text is not supported when you import or export CSV files. If the artifacts that you are importing or exporting contain styles or formatting, the resulting content is plain text. (The rich text in spreadsheet files is imported or exported.)
  • Exporting and importing of horizontal lines in text is not supported. If you include horizontal lines in a text artifact, export that artifact to Microsoft Excel, and then import the file, the horizontal lines are lost.
  • If you modify text format in a Microsoft Excel file, but do not change the text itself, when you import the file, those format changes are not imported. The format is only changed when the text is also changed.
  • Bullets that are used within the cell of a Microsoft Excel spreadsheet are not supported. If you export or import these files, the bullets are removed.
  • Text alignment is not supported when you import or export artifacts.
  • Indents are not supported when you export CSV files or Microsoft Excel files. If you import the CSV files or Microsoft Excel files that you exported, the indent is removed and the content is left aligned. If you are working in a configuration-enabled project area, these changes are flagged as unexpected differences.
  • When exporting a module view, if you select the Include links, tags, and comments from base artifacts option, the base artifacts themselves are not exported; only the bindings are included in the exported file.
  • You can export artifacts to a CSV or spreadsheet file, change the attribute values in the file, and then import that file back using Update artifacts that match entries and create artifacts for new entries. The Update artifacts that match entries and create artifacts for new entries process is only for creating new entries or for updating attributes for artifacts that are part of the module. If you remove any of the exported artifacts from the module and then import the modified file the update option will not work.
  • Nested levels are not supported when importing or exporting a Microsoft Excel file. Even if there have been no changes to the original artifacts comparison with the original artifact will indicate changes.
  • You can export a module with identical artifact IDs. When you import a module, you cannot delete the artifacts with the identical IDs that are removed from the exported file.