You will be sent an email when your MS Word specification file import is complete, or if it fails. In both scenarios, the email contains a report.
When the import is successful, the report will tell you what to check in Chorus.
When the import fails, the report will tell you why.
There are four key columns to the report.
- Imported - This will be TRUE when the section was imported and FALSE when it fails.
- Note type- Will say either 'Error' or 'Information'.
- An Error will indicate the reason for the section to fail the import.
- Information is something you should check and possibly correct before using what has been imported in a live project.
- Notes - a description of what needs to be checked.
- Location - the location of the MS Word file this should be checked in.
Known Errors - these will cause the file not to be imported
- Missing content - no Section found.
- Zip file cannot contain another zip file.
- Zip file is empty.
- Your zip contains X files. The zip file cannot contain more than Y files.
- File uploaded was too large.
- Unsupported file type: We currently support .docx files or .zip files containing multiple .docx files.
- Unable to connect to the database, please retry your import.
- There was an unknown error.
- Missing content, no title in the section.
Known Information - Specifications tend to be structured documents
The platform has been designed to alert you when it cannot identify data as a Section title, Group, Clause or Row. Usually, this is because the style formatting has not been applied throughout the document. It is important to check when this is reported, as it could mean that not all of the document was imported into the correct fields in the specification.
- The section is valid. This means no issues were found.
- No groups (Heading 2) found after section title (Heading 1).
- No clauses (Heading 3) found after group title (Heading 2).
- No rows (Normal) found after clause title (Heading 3).
- Unable to identify the element as a \section\group\clause\row.