How copy and move affect links

This topic contains the rules that apply to links when you copy or move objects in the database explorer or module windows.

When you use cut and paste:

Table 1. How copy and move affect links
If you Then
Move an object, module, folder, or project that contains links All the links are preserved.
Copy an object that has links If you copy the object within the same module, out-links are copied. Each copied out-link uses the same link module as the original out-link.
The following rules apply to in-links:
  • If you copy the object to another module, links are not copied.
  • If you copy the object within the module and you have modify access to the source object, the in-link is copied.

Links are not copied if the link uses a mandatory linkset pairing that goes through a link module that has one-to-one mapping.

External links are always copied because all the information about them is contained in the object.
Copy a folder, project, formal module, or descriptive module that contains links In-links are only copied if you also copy the module that contains the object at the other end of the link.
Out-links are always copied.
  • If the out-link uses a link module that is being copied, the out-link in the copied module uses the copied link module.
  • If the out-link uses a link module that is not being copied, the result depends on whether the link module has the same parent project or folder:
    • If the link module has the same parent, a link module with the same name as the original link module is created in the new location. The out-link in the copied module uses the new link module. If a link module with the same name as the original link module exists in the new location, it is used.
    • If the link module has different parent project or folder, it is used for the copied out-link.
External links are always copied because all the information about them is contained in the object.

Feedback