The Import function of Database Management is a powerful tool that modifies data in the current configuration. It is recommended to ALWAYS back up your data before executing a data Import.
All records associated with the selected Work Order(s) are transferred by default.
Fig. 01 – Database Management Utility – Import Work Orders
Select IMPORT from Selected Source to Current Configuration > browse to the file location containing the MicrovellumFactory.sdf to be imported > select the MicrovellumFactory.sdf.
Select the Work Orders tab.
The middle panel is populated with data from the database selected in Step 1. Select the Work Order(s) to be imported from this central panel.
When pulling from an archival database, chances are not everything in the external database needs to be imported. The middle panel in the image above allows you to select only the items you wish to import. The items specified appear in the panel on the right. Items can be selected from multiple categories at once.
Select Transfer.
Troubleshooting: "The path is not valid. Check the directory for the database."
This message appears when the Work Order you selected is listed correctly in the middle panel, but the underlying work order database cannot be found at the location the source Factory database expects.
Each Work Order stores its data in its own MicrovellumWorkOrder.sdf file inside a work order folder. The Factory database records the path to that folder. When you import on a different machine, that recorded path is resolved against your machine — and if the folder is not there, the import fails even though the Work Order appears correctly in the list.
NOTE: The path shown in the error message is the path Microvellum is looking for — it is not a file you selected. Use it to identify what is missing.
What to check, in order
Confirm the work order folder came across with the database. The exported package must include the work order folder, not just the .sdf file on its own. If it is missing, ask the sender to re-send the complete exported folder.
Confirm the path is reachable from your machine. If the path in the error message points to a drive letter or network share you do not have — for example a local C:\ path from the sender's PC, or a mapped drive that only exists on their network — your machine cannot resolve it.
Recreate the path if the folder is available elsewhere. Placing the work order folder at the exact path named in the error message will allow the import to complete.
Check the folder name for trailing spaces or unusual characters. Long project folder names copied between machines are a common source of mismatches.
A different error with the same wording
If you see "Path is not Valid" when launching Microvellum rather than during an import, that is a configuration path issue rather than an import issue. See Software Troubleshooting: Installation, Path Not Valid, Data Decryption.
Resolving Duplicates
When importing from a database that includes data duplicated from the Factory Database, like an archival database, the Resolve Duplicate Names window appears.
Fig. 02 – Resolve Duplicate Names
There are three options to resolve duplicates:
Skip – Does not change the existing item, and an additional item is not added. The item is ignored.
Replace – Replaces the item in the target location that has the duplicate name.
Keep Both – Appends to the target location. A new name must be given to the item.
Fig. 03 – New Name