14.2 Import Objects

To import objects you need to provide the same Object Storage connection that you had used for the export operation.

Note the following about the import process:

• Projects - To import projects, you can choose whether you want to overwrite the data in the repository or merge the matching container objects with the objects that are being imported.
  • Overwrite - If there is a match in the repository, all the dependent child objects will be overwritten by default.

    If there is no match, the project along with the child objects will be copied into the repository.

  • Merge - If the project exists in the repository, but the dependent child objects have no match, all the child objects in the repository will be merged with the new child objects that are coming through the import process.

    If the project exists in the repository, and the dependent child objects have a match, all the child objects in the repository will be overwritten with the new child objects that are coming through the import process.

    If the project does not exist in the repository, the project along with the child objects will be copied into the repository.

• Connections - For connections that have a match in the repository, the import process updates only the advanced properties of the connection in the repository along with the connection name. Credentials such as the schema name, passwords, and connection URL are persisted as is in the new environment. You can use such connections without any modification in the target repository.

  For connections that have no match in the repository, credentials such as the schema name, passwords, and connection URL are not carried over during the import operation. Post import, you need to update the credential information for such connections. You also need to make sure that you create a schema user in the database along with the required tables created for the schema user, which you may use as a data entity in dataloads, dataflows, workflows, and schedules.

• Data Loads, Data Flows, and Workflows - For these objects if there is a match in the repository, all the objects will be overwritten by default.
• Schedule - The status for schedules that have no match in the repository are set to Inactive. You need to update the connection information that is associated with the schedule, and then set the status of the schedule to Active.

To import objects:

1. From the left pane, click the Home tab. Click Import.

   The Import dialog box appears.

2. From the Object Storage Connection drop-down, select the connection that you had used for the export operation. See Export Objects.
3. From the Import File Name drop-down, select the exported file.
4. Choose one of the following import options:
   • Merge - Choose this to merge the objects that are already in the repository with the objects that are coming through the import process. This option is only available for container objects such as Projects.
   • Overwrite - Choose this to replace the objects that are already in the repository with the objects that are coming through the import process.
5. Click Import to start the import operation.

   A confirmation prompt appears when the import operation completes successfully.