Import objects

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

1. On the Home ribbon, select Import.

   Note: Or, you can select Galaxy, then select Import.

   

2. Select Objects, then select Objects from package. The Importing objects dialog box appears.

3. Browse for the file with either an .aaPKG or an .aaPDF extension. You can select more than one file. Select Open. The Import Preferences dialog box appears.

   

4. In the Objects with same Tagname and Codebase as an existing object area, select one of the following:

   • Skip: Do not import leaves the existing object unchanged.

   • Overwrite objects if the imported configuration version is higher replaces the existing object with the object being imported if the imported object has a newer configuration. This is the default.

   • Overwrite objects regardless of configuration version replaces the existing object regardless of whether the existing object has an older configuration or the same configuration.

5. In the Base Templates with a different revision number in the Codebase or a different minor version area, select one of the following:

   • Skip: Do not migrate - objects with an older codebase are not migrated when a newer codebase exists in the Galaxy.

   • Migrate - objects with an older codebase are migrated when a newer the replacement object.

     For more information about migrating, see About importing.

6. In the Objects with same Tagname but with a different Codebase area, select one of the following:

   • Skip: Do not import leaves the existing object unchanged.

   • Rename object in Galaxy imports an object with a matching tagname but a different codebase from the existing one. The existing object is not overwritten but is renamed.

   • Rename importing object imports an object with a matching tagname but a different codebase from the existing one. The existing object is not overwritten. The imported object is renamed.

   Note: This set of options applies to objects of the same type such as Automation Objects with the same tagname. This option is not designed to flag occurrences where an Automation Object and a graphic have the same tagname. However, the progress dialog and logger will display a message that duplicate tagnames have been found, and the duplicate tagnames will be listed in the Logger.
   
   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. After the import is complete, rename either the object or graphic that has the duplicate tagname to avoid potential issues.

7. In the Template Protection Change Management area, select the checkbox to prohibit overwriting an unprotected object with a protected object (default). Clear the checkbox to allow overwrites.

8. Select Import. The import process starts.

9. When the import process is complete, you can start using the objects you imported.