Data Profiling

Back Next

Import profiles

You can import all the profiles from an export file or select the profiles that you want to import.

When you import a profile, you specify the following information:

The profiles in the export file that you want to import and the projects in which to import them.

Whether to overwrite profiles in the target project with profiles in the export file when there is a name conflict.

To import profiles, you need the following privileges and permissions:

Your user role must have privileges to import profiles.

If you import a profile into the target project as a new profile, you must have create, update, and read permissions on the profile.

If you overwrite a profile in the target project, you must have update and read permissions on the profile.

Additionally, to overwrite a source-controlled profile in the target project, you must have the profile checked out. The target organization must have all of the required licenses for the profiles being imported. The

Import Assets

page lists the profiles that are in the export file. You can select which profiles you want to import, and then specify which project to import the profiles to. You can accept the default project, which is the same project name as the source project, or you can select a different project. If the project does not exist in the target organization, Informatica Intelligent Cloud Services creates it.

To import profiles that include scorecard assets, you must make sure the following prerequisites are met:

You must have the Intelligent Cloud Data Management and Data Governance and Catalog licenses.

The Intelligent Cloud Data Management user must have the Governance user role assigned.

Profile name conflicts

You can specify how Informatica Intelligent Cloud Services handles profile name conflicts when the export file contains profiles with the same name as profiles in the target project. You can choose whether to overwrite the profiles in the target project or use the existing profiles in the target project. To see how the import handles any profile name conflicts before you start the import job, you can test the import on the

Import Assets

page before you import the profiles. The import action displays in the

Status

column for each asset. You can filter the list of profiles by asset name, asset type, or status.

The following image shows a profile and the import action to be performed when overwrite existing profile is enabled: The image displays a profile and the import action that you can perform when overwriting an existing profile is enabled.

Replace a profile definition

You can overwrite a profile definition during the import task for profiles that already exist. After you import the profile definition,

Data Profiling

does not delete or replace the existing profile results. If you import a profile definition that has different configuration details such as the connection name and source objects. In that case, you cannot compare the new profiling results with the existing profile results.

The following images display a sample profile definition and profile results page after you replace the profiling task: