This feature:
Copies resources if they do not exist on the target instance.
Updates only the parent resource if the parent and dependent resources exist on the target instance. Original and copied resource items have the same name and creation date.
For example, if a Segment having a Visited a Specific Landing Page filter for a landing page is copied from one instance to another, the Segment and the landing page used in the segment filter is copied to the destination instance. If the Segment already exists in the destination instance, it is updated with any changes from the source instance. If that landing page already exists in the destination instance, it will not be updated with changes from the source instance.
Note
If a copied item exists in the destination instance (identified by the item’s UUID or alias), the system overwrites the existing item with the copied item. To ensure accuracy of the copies, you must create dependent resources in the source instance and copy the resources through the resource copy feature. If you create a resource with the same alias of a different resource of the same type, the destination resource might be overwritten by any copy that references it.
Important
Acquia recommends you to not use the same alias for different resources belonging to the same resource type.
To copy a resource from one instance to another:
Navigate to the Instance Overview page of the instance you want to copy the resource from.
Locate all the instance resources listed on the right of the page.
Click the Copy icon for the type of resource that you want to copy in the Instance Resources section.
In the pop-up window, select the resource(s) to be copied, and the target instance(s).
Note
You can select multiple items to be copied. Once you make your initial selection, you can either begin typing or select an option from the drop-down list. To remove a selected item, click the
xicon.Click Save.
The system initiates the copy process, notifies the user, and displays a confirmation message in the user interface. If the copy operation fails because of certain conditions, the system displays a user-friendly error message with the item(s) that caused the failure. For example, a missing token in the source or destination, or a custom field missing.
Resource copy scenarios
If you have a segment email that embeds a landing page, a global token, and an asset, and you want to copy the email over to other Campaign Studio instances, you can resource copy the email.
For the first time copy, all dependencies are copied.
For a subsequent copy, only the top-level entity and tightly-coupled entities are copied.
In this example scenario:
Dependencies refer to the landing page, global token, and asset.
Top-level or main entity refers to the email.
Tightly-coupled entities refer to segment, segment filters, campaigns, and campaign events.
Scenario | Expected |
|---|---|
| Only the parent resource should be copied once the parent entity exists in the destination. |
| Updates in the parent resource should be copied. |
| The parent resource should be copied successfully. |
| Updates in the parent resource should be copied. |
| The parent resource should be copied and the dependent resource should show no change. |
| The parent resource should be copied and the dependent resource should show no change. |