Table of Contents

Search

  1. Preface
  2. Project and asset management
  3. Source control
  4. Asset migration
  5. Bundles

Asset Management

Asset Management

Asset name conflicts

Asset name conflicts

You can specify how
Informatica Intelligent Cloud Services
handles asset name conflicts when the export file contains assets with the same name as assets in the target project. You can choose whether to overwrite the assets in the target project or use the existing assets in the target project.
To see how the import handles any asset name conflicts before you start the import job, you can test the import on the
Import Assets
page before you import the assets. The import action displays in the
Status
column for each asset. You can filter the list of assets by asset name, asset type, or status.
The following image shows a list of assets and the import action to be performed when overwriting existing assets is enabled:
The image of the Import Asset page shows nine assets and the projects in which the assets are to be located. The Status column shows that during the import, Informatica Intelligent Cloud Services creates one of the assets because it does not exist in the target location. Informatica Intelligent Cloud Services overwrites the other assets because assets with the same name exist in the target location.
If the target organization has connections or runtime environments with the same name as those in the export file,
Informatica Intelligent Cloud Services
uses the connections or runtime environments that exist in the target organization.
Informatica Intelligent Cloud Services
does not overwrite the connections or runtime environments in the target organization.

0 COMMENTS

We’d like to hear from you!