When the PowerCenter Client imports the object instead of the shortcut, the imported object does not inherit any changes you make to the original object in the source repository. The XML file defines the metadata for the object.

Use the imported object as you would the original object. However, if the object is a source definition, you might need to rename the source definition.

For example, you export a shortcut named Shortcut_To_Employees and you also export the referenced object. You use the Designer to import the shortcut into a different repository. In the Import Wizard, you choose to import the shortcut, but you do

not

import the referenced object. Also in the Import Wizard, you choose a folder in the destination repository to specify the location of an existing referenced object. However, the folder does not contain an object with the same name as the referenced object specified in the XML file.

The PowerCenter Client does not find an object with the same name in the folder you specified, so it imports the actual object instead. The Designer creates a new source definition in the destination folder named Shortcut_To_Employees. This source definition is a copy of the original object, and is not a shortcut. When you use the source definition in a mapping, the default SQL used to extract data from the source defines the source as Shortcut_To_Employees. If the source table in the source database is named Employees, you must rename the source definition (Employees) or enter an SQL override for the source qualifier connected to the source definition (renaming the source table Employees) for the Integration Service to extract source data.