Import Dependencies

To access this function :

Using the Dependencies panel (Import Dependencies group), click Import.

In order to combine data from separate projects you can add design files from multiple projects to a single project in UG. If data has already been sequenced then dependencies can be used in the new project using the Import Dependencies function.

This would normally be the case if you have already combined design files and need to import dependencies for the additional data, where that data has already been sequenced in another project.

Before you import dependencies from another project, you will need to ensure:

The remote data is sequenced, i.e. dependency data exists for the associated design data. The Dependencies folder of the remote project(s) will be assessed and, if it is possible to import the remote dependency information into the current project, it will be imported.
A dependency layer exists in the current project that matches the layer of each dependency in the remote project.

Both manual and automatic (rule-based) dependencies can be imported. By default, only manually-crafted dependencies will be imported, but you can choose to import all dependencies generated by the rules of the remote project if you wish.

It is not possible to generate duplicate dependencies with this task and existing dependencies will be preserved.

You cannot import dependencies unless the selected project is different from the one currently loaded.

Field Details:

The following controls are used to manage the import of dependency data:.

Should Import Rules Based Dependencies: disabled by default, this option will allow you to import dependencies created in the remote project by spatial or attribute-based rules.

Import: select this button to display a project browser. Use it to select an existing Studio UG project files containing dependencies you wish to import..

Show output: if selected, a table is displayed indicating the progress of the import process. This is split into 3 sections:

Errors: items that prevent the successful import of any dependencies will be listed here. These should be resolved before you continue.

Warnings: unexpected items, or where specific items within the import scope could not be imported (e.g. where a target dependency layer cannot be found in the current project) are listed here. You should review the contents of these messages and resolve any blocking items before you continue.

Messages: status messages indicating progress of data import.

	Related Topics
	The Dependencies Panel Dependency Layers Spatial Dependencies Attribute-based Dependencies Auto Dependencies - Golden Rules