SOLVED

.

Go to solution
Highlighted
Anonymous
Not applicable

.

.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Champion Alumni

Re: Cloning programs across workspace

Also be sure that you’re not referencing other assets (smart lists, forms, emails, landing pages) that aren‘t accessible in the other workspace. Smart lists and snippets, like template, can be shared. Emails, LPs, and forms cannot - and will need to reside locally within the program you’re cloning.

View solution in original post

3 REPLIES 3
Highlighted
Level 7

Re: Cloning programs across workspace

I think the issue here is that the templates used in the assets are not available in the other Workspaces, you have to also Share the templates across the Workspaces so you can clone assets.

The steps are:

In your Global Workspace, go to Design Studio, then in Landing Pages, create a folder under templates, name it Shared Templates, drag in all the templates you want to share, then right click and Share Folder and select your other Workspaces.

Do the same steps for Email Templates.

Once this is complete, try Cloning the original template and you should get no errors. Please note the error message is a bit misleading, as it doesn't actually mean that the assets are being used somewhere but more that the templates don't exist.

Highlighted
Level 10 - Champion Alumni

Re: Cloning programs across workspace

Also be sure that you’re not referencing other assets (smart lists, forms, emails, landing pages) that aren‘t accessible in the other workspace. Smart lists and snippets, like template, can be shared. Emails, LPs, and forms cannot - and will need to reside locally within the program you’re cloning.

View solution in original post

Highlighted
Level 1

Re: Cloning programs across workspace

This trick is what I used in moving a program from workspace A to workspace B and it works. It really helped to know that "Asset is being used" is a misleading error message, it is. Moving templates in shared folders can be used as one of the best practices for program creation, to help smooth transition of programs among different workspaces. Thanks, again!!! 🙂