Exporting Hierarchical Components
Hierarchical components can have dependent definitions such as symbols that reside in other library types. Consequently, when exporting a hierarchical component, you can export referenced symbols, models, and packages.
When sending exported data such as libraries to third parties, or when relocating exported data, be sure to include all related files.
Project variables and project datasets used in designs represented by hierarchical components are saved to the library with the component and restored when the component is used. If the variable or dataset already exists in the project (determined by name), the library version is ignored. When creating project variables or datasets for hierarchical component designs to be saved in a library, make sure the names of the variables and datasets are appropriate and not likely to clash with those of other hierarchical components or common defaults.
- When you select a hierarchical component in the Edit Libraries dialog box and click Export to Library, the Export to user library dialog box appears.
- Choose the location and file name for the .aclb library file that will contain the exported components. Click Save to confirm your choice. If the library does not exist, you are prompted to create a new one.
The Export Hierarchy dialog box lists the component and dependent object Definitions for the exported components. Dependent objects that can be exported include:
- Symbols (exported as .aslb files).
- Models (exported as .asmd files).
- Packages (exported as .apkg files).
Buttons in the Library column open the Export to user library dialog box where you can browse for a library file in which to store the definition, or create a new library. The library file type and extension correspond to the Library Type listed for each object. The Library field button name is that of the library in which the definition currently is stored, and is blank if no library is yet assigned. By default, the Library field names are set to the same library.
Use the check boxes to choose:
- Which definitions to Export.
- Whether to Overwrite existing definitions in the target library.
- Whether to Export Solution data for schematic components. Solution data is saved in a .results folder instead of a library file.
- Click OK to confirm your selections. The definitions (and solution data, if applicable) are saved in the locations and files you chose.