Needs & Requirements

Import

Brings requirements and models in from files in four steps: Configure → Select → Customize → Preview.

Where to find it

Word (.docx): headings and list numbering become the outline; text, lists, pictures and tables join the item they follow. A requirements table can become one entity per row. The original file is kept on the document.
Excel / CSV: any columns; pick the sheet of a workbook. CSV encoding is detected (UTF-8, Windows-1252, Shift_JIS, Big5, UTF-16); choose the date format for date columns. Save .xls files as .xlsx first.
ReqIF (.reqif, .reqifz) and UML/SysML (.xmi), including relationships.
Project files (.inno, .json, .xml): Holarch project and document exports, .inno ZIP files and XML exports, with options for comments, history, diagrams and the schema. IDs are always reassigned.
Plain Text (.txt) or pasted text.

Match existing entities by Global ID, Name or Number updates matching entities instead of adding copies; only mapped columns are written. Name and Number matches also require the same class.
Phrase rules assign a class to any entity whose description contains a word or phrase.
Outline format for Word and text: automatic, numbered or lettered lists, multi-level (1.1.1, 1. a. i., I. A. 1. a), DoD lists or a custom format with up to 6 levels.
A column named after a label group (for example Verification Method) maps to labels.

To update requirements from a spreadsheet: export from the Database (it includes Global ID), edit, then import with Import as: None and match by Global ID.
One undo removes the whole import.