Common causes of failed imports
Your MS Word file will fail to be imported when:
- A section title cannot be found (i.e. there is no text in the document styled as 'Heading 1').
- You will receive an email stating that 'There was a problem importing your MS Word specification'.
- The report attached will be called 'missingheading1.xlsx' and state 'Missing content, no sections in ImportData'.
- Please see 'Importing Microsoft Word specifications' for what a successful import should contain, and tips for how to structure your MS Word file.
- The file being imported is not supported. The platform supports:
- Single MS Word (.docx) files not larger than 30MB.
- Zip files containing fewer than 100 files.
- Zip files not containing another Zip file.
- Zip files not containing a directory. When you zip a set of files, select the files and zip them. Avoid zipping to the folder that they are in.
- This import route It does not import PDF files.
- Please use 'Importing PDF & MS Word (unstructured documents
What to do when your file(s) fail to be imported
If your MS Word file was not imported successfully, please follow these steps and try it again:
- Check your email - once your MS Word file has been processed, you are sent an email to confirm that it has been imported, or that the import has failed. The email contains a report about the imported file. Chorus validates the file being imported, and will set out in the report what has failed the validations.
- Most files will fail to be imported if the platform cannot find where the section starts because nothing in it is styled with a 'Heading 1'.
- Reformat your MS Word specification and retry importing it - go back to your file in MS Word (or a copy) and style it so that it follows the 'H1, H2, H3, H4' and 'Normal' style hierarchy that the platform is looking for.
- Please refer to 'Importing Microsoft Word specifications' for a detailed overview of the styles and some simple steps to structure your document in this format.
- Please refer to 'Importing Microsoft Word specifications' for a detailed overview of the styles and some simple steps to structure your document in this format.
How to get help
If reformatting your specification does not solve the problem, please contact Customer support.
To help our teams troubleshoot the problem it will be helpful to share the document that you are importing and the failed import email that you received from Lattira Spec or NBS Chorus.
The email contains a Job ID - e.g. dc44a655-2959-4972-bc77-fde81163b56c – which helps with our investigations.