Import from MS Excel

Import New Objects

You can import a CSV file storing document objects into an existing ReqView document. ReqView preserves the tree hierarchy of imported document objects and values of custom attributes.

The CSV file should contain the following columns:

  • “level” — an integer number determining the hierarchy level of imported objects; if the level column is not provided, then CSV rows are imported as a flat list
  • “heading” — heading of document sections displayed in the Description column
  • “text” — text description of requirements displayed in the Description column

CSV columns representing an imported custom attribute should store the attribute ID (e.g. “status”) in the header row and values matching the definition of the custom attribute in the following rows.

No CSV column can be named “id” as ReqView assigns unique IDs automatically for the new imported objects.

Example:

ExcelCSVImportData.png

Follow these steps:

  1. In MS Excel, change column names in the first row to match the IDs of ReqView internal attributes “heading”, “text”, “level” or custom attributes, for example “status”, etc.

  2. In MS Excel, open Save As dialog and select CSV UTF-8 (Comma delimited) (*.csv) file type available in the latest Excel versions or Unicode Text (*.txt) file type available in Excel 2016 and older versions.

  3. Open a ReqView project and select a reference document object for placing the imported objects. Then click File, mouseover Import, mouseover CSV File, and select whether you want to import new objects Before, After or As Children of the selected object.

  4. Choose the CSV (or TXT) file that you saved in Step 2.

    Note: If ReqView does not create new document objects or creates empty document objects then double check if the CSV header contains correct IDs of ReqView attributes. For instance, if your CSV file contains column “Description”, which is ignored by the importer, then split this column to columns “heading” storing section headings and “text” storing requirement description.

Update Documents

You can import a CSV file with attribute updates or outgoing traceability links of existing ReqView document objects. For example, you can update the status of tests (failed or passed) or the FMEA rating of project risks.

The CSV file must contain the column “id” storing the identifier of an existing document object. If it is empty then a new object is added at the end of the document.

CSV columns representing custom attributes should store the attribute ID (e.g. “status”) in the header row and values matching the definition of the custom attribute in the following rows.

CSV columns representing outgoing traceability links should store the link type ID (e.g. “satisfaction”) in the header row and list of linked target object IDs (e.g. “NEEDS-12,NEEDS-34”) as values in the following rows.

Example:

CSVUpdateFMEA.png

Follow these steps:

  1. In MS Excel change column names in the first row to match the IDs of ReqView internal attributes “id”, “heading”, “text”, “level” or custom attributes, for example “status”, etc.

  2. In MS Excel, open Save As dialog and select CSV UTF-8 (Comma delimited) (*.csv) file type available in the latest Excel versions or Unicode Text (*.txt) file type available in Excel 2016 and older versions.

  3. Click File, mouseover Import, mouseover CSV File, and select Update Document.

  4. Choose the CSV (or TXT) file that you saved in Step 2.

    Note: If ReqView does not update the document objects then double check if the CSV header contains correct IDs of ReqView attributes. For instance, if your CSV file contains column “Description”, which is ignored by the importer, then split this column to columns “heading” storing section headings and “text” storing requirement description.

Roundtrip Synchronization

The following steps describe an example workflow for exporting documents into CSV, importing back changes and new objects from an updated CSV file, and maintaining information about the source of imported objects (name of CSV file) and the import state.

  1. Define custom attributes: In the exported document, create a custom attribute importSource of string type storing to the name of the CSV file from which the object was initially imported, and importState of enum type storing import state (for example “New” for new objects), see also Custom Attributes.

  2. Export the document into CSV: Click File, mouseover Export, and mouseover CSV File. Provide it to a reviewer who can change existing objects or add new rows with empty ids which will be imported as new objects.

  3. Import the updated CSV file: Click File, mouseover Import, mouseover CSV File, and select Update Document. New document objects (without IDs in the CSV file) will be placed as a flat list at the end of the document and they will automatically get unique IDs.

  4. Update custom attributes: Change the importSource attribute of the new objects to the name of the CSV file that is used for import. After you move each new object to the right place, change the value of the importState attribute to “Acknowledged”. You can also select all the new objects and change the value of custom attributes importSource and importState for all of them at once. The history contains the change records for attributes importSource and importState, providing more information about who imported each new object, when, and from which CSV file.

  5. Optionally, you can mark unwanted new objects as deleted and purge them permanently from the document.

Updated for version 2.7.0