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

Importing a Foundation Library into Older Structured Library:

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.
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
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
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:

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.
Graphic Issues: Graphic files are general 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 a Component library into another Component library is not recommended if they are the same version (I.E 50.7 into another 50.7)

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:
2. 1. Products
  2. Subassemblies
  3. Room Components
  4. Materials