About importing

You can reuse objects from another Galaxy in your Galaxy. This saves you a lot of time if the objects are already set up in another Galaxy.

Importing instances previously exported from a Galaxy retains previous associations, when possible, such as assignment, containment, derivation, and area.

You can import objects from exported .aaPKG files or from an .aaPDF file. An .aaPDF file contains the configuration data and implementation code for one or more base templates. It is created by a developer using the Application Object Toolkit.

You cannot have two objects with the same name or more than one copy of the same version of an object in the same Galaxy. When you import an object, you can choose how you want naming and version conflicts handled.

You should upload any pending runtime changes before importing a new version base template if instances of the template are deployed. This saves changes made at runtime to the Galaxy database. To upload runtime changes:

• Select the Upload changes option on the ribbon bar.

• Right-click on the Galaxy name and select the Upload Changes option from the context menu.

  Note: The Application Server version is not the same as the Codebase version. Objects with newer Codebases can be imported.

Imported templates are listed in the proper folder in the Template folder as defined in the object. Imported instances are shown in the Application views.

The following post-import rules apply:

• If a folder does not exist, it is created.

• If the object belongs to a security group that does not exist, it is associated with the Default security group.

• If the object belongs to an area that does not exist, it is associated with the Unassigned Area.

• If the host to which the object is assigned does not exist, it is assigned to the Unassigned Host.

• If an object has the same name as a graphic, a message is displayed in the progress dialog and in the logger that duplicate tagnames have been found. The duplicate names are listed in the logger. Rename either the graphic or object.

  Note: As of System Platform 2023 R2 SP1, you are blocked from duplicating tagnames between graphics and Automation Objects. However, duplicate names are not blocked during an import operation. We recommend that you rename any duplicated object/graphic names to avoid potential issues.

• If you selected Migrate from the Import Preferences dialog box, the migrated objects are marked with "software upgrade required" if they are deployed. These objects will be upgraded when the objects are redeployed.

• If you import a new version of an existing instance, the new version is marked as requiring deployment if the existing object is already deployed.

  Notes: Libraries, Client Controls, and OMI Apps compiled with any version of .NET Core (including .NET 5, 6, 7, or 8) are not supported in System Platform. While the system may indicate a successful import, these components will not appear in the IDE or be usable in design time or at runtime.
  
  Some .NET standard libraries may work, but compatibility is not assured. For the best results, we recommend only using libraries compiled with .NET Framework 4.8.1.