Skip to main content

Common Issues Associated with Importing Libraries

Common problems when importing Foundation or Component libraries into another library structure, and what to check if your tool file looks different after importing older projects.

J
Written by Jordan Munoz

The software, previously referred to as "Toolbox", was rebranded to the name "Microvellum" in the year of 2025. If your software version was released prior to the year 2025, you may see certain settings with different names reflecting this change, such as 'Toolbox Setup' becoming 'Microvellum Setup'.

This article will outline the common issues associated with importing libraries.

Importing a Foundation Library into Older Structured Library:

  1. F-Workbook: Foundation library has a specific F-Workbook that will need to be migrated into the database if importing Foundation into the Component library.

  2. Material Library Issues:

    1. Hardware is library specific

    2. Hardware machine tokens is library specific

    3. Hardware Graphics can be library specific

    4. Formula driven materials are library specific and won’t be usable outside its designated library

    5. Material pointers will need to be redone

  4. Graphic Issues: Graphic files are generally library specific

    1. All drawings could be scaled incorrectly

    2. Router Profiles could have changed

    3. Help images could be wrong

    4. Hardware drawings have been modified for foundation library

  6. Drawing Templates: Each library has a specific template. They will need to both exist in the drawing templates folder or be customized to be merged into one.

Importing Component Libraries into Foundation Library Structure:

  1. Material Library Issues:

    1. Hardware is library specific;

    2. Hardware machine tokens is library specific;

    3. Hardware Graphics can be library specific;

    4. Formula driven materials are library specific and won’t be usable outside its designated library;

    5. Material pointers will need to be redone.

  3. Graphic Issues: Graphic files are generally library specific.

    1. All drawings could be scaled incorrectly;

    2. Router Profiles could have changed;

    3. Help images could be wrong;

    4. Hardware drawings have been modified for the Foundation library.

Importing Component Libraries into other Component Library Pitfalls:

Importing a Component library into another Component library is not recommended if they are the same version (I.E 50.7 into another 50.7)

  1. Typically, issues can arise when a custom library is imported into a default library. The following are reasons to avoid importing Component libraries into other Component libraries.

    1. The LinkIDs are the same. This causes issues with:

      1. Products

      2. Subassemblies

      3. Room Components

      4. Materials

After Importing Older Projects, My Tool File Shows Different Tools or Diameters

If other users on the same server are not affected, check this first: go to Microvellum Settings > Options > Toolfiles and confirm that your workstation has the same default tool file set as your colleagues. If the name matches but the tools or diameters do not, open a support case before you process any work orders.

Note: The Library Restore Utility undoes a Library Update Utility run. It does not undo a project or library import.

Did this answer your question?

Related Articles