NOTICE: The Import function of Database Management is a powerful tool that modifies data in the current configuration. ALWAYS back up your data before executing a data Import.
The articles in this section of the Knowledge Base involve importing and exporting from the Database Management window. For general information regarding the Database Management tool, or how to access it, see Database Management Utilities (Overview)
This simplified article provides a brief tutorial for importing a Project using the Database Management Utility.
All records associated with the selected Project(s) are transferred by default. These records include Rooms, Locations, Drawings, Products, Subassemblies, Specification Groups, Project Level Materials, Primary Processing Stations, and Primary Tool Files.
Fig. 01 – Database Management Utility – Import Project
- 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 Projects tab.
- The middle panel is populated with data from the selected database. Select the Project 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.
When importing a project, the following Additional Options are available:
Fig. 02 – Additional Options when Importing a Project
- Transfer All Hardware Drawings – Check or uncheck this box to control the automatic transfer of all hardware drawings associated with a library or Project. If the materials are not transferred, errors may be generated after the items have been imported, when working with the data on another system.
Any desired Additional Options should be selected
BEFORE the transfer.
When importing from a database that includes data duplicated from the Factory Database, like an archival database, the Resolve Duplicate Names window appears.
Fig. 03 – 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. 04 – New Name
When a project is imported, an import category is added that contains the Project. This appears in the tree-view:
Fig. 05 – Import Category