You can copy a shortcut to other folders. When the Designer copies a shortcut, it creates another shortcut in the new folder. The new shortcut points to the original object used by the original shortcut.

The Designer cannot copy a shortcut when it cannot find the object that the shortcut references. This might occur if, for example, you copy a local shortcut from one repository to an unrelated repository.

When the Designer cannot successfully copy a shortcut, it creates a copy of the shortcut object. The copy of the shortcut object is identical to the original object the shortcut references. Unlike an actual shortcut, the copy will not inherit any changes to the original object. Use the copy of the shortcut as you would the original object. However, if the object is a source definition, you might need to rename the source definition.

The following table lists the results of copying global and local shortcuts to different repositories:

For example, if you copy a shortcut named Shortcut_to_Employees from one standalone repository to another, the Designer creates a new source definition in the destination folder named Shortcut_to_Employees. This source definition is a copy of the original shortcut, but 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 is named Employees in the source database, 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.

For example, the fourth row of the table indicates when you copy a global shortcut (a shortcut to an object in a global repository) from one local repository to another local repository in the same domain, the Designer creates a global shortcut to the object in the global repository.