Re-enable the ability for cloned programs, that contain empty values, to be moved to other workspaces

[Dan_Stevens_]

UPDATE (3/5/2016): We had to rebuild all of our program templates for this to work again.  Details are contained here: Cloning programs across workspaces - be aware of a "fixed" capability that no longer works

UPDATE (3/2/2016): This functionality is broke once again.  See detailed post here: Cloning programs across workspaces - be aware of a "fixed" capability that no longer works

UPDATE (12/19/2014): This is no longer an issue now that you can clone directly across workspaces (as a result of the December 2014 release).

The details behind this idea are part of a separate post here: https://community.marketo.com/MarketoDiscussionDetail?id=90650000000PytbAAC

To summarize, Marketo Engineers recently enabled validation on programs when Cloning and Moving them. As a result, you can no longer have triggers, filters or flow steps that have empty values.  Going forward, you must remove the filters, triggers and flows steps, move/clone the program, then re-add those filters, triggers and flow steps once the Program is cloned or moved.  This basically defeats the purpose of cloning a program.

This has destroyed our team's workflow and overall processes of how we operate 20+ workspaces within Marketo.

[Luis_Paez3]

This is a good idea - I've seen various deficiencies when using a "shared" workspace with other team-specific workspaces.  The approach that you think would work when thinking about how shared workspace should work, isn't reflected in today's implementation.   Marketo's execution abilitywould be strengthened if they put more thought and product ownership on this piece of the puzzle.  

[Jamye_Breidenba]

Hi Dan,

I wish I read your original post sooner describing the feedback from Marketo. We have a very similar setup in our instance where there is a central workspace with program templates for our other regions to clone and move to their own workspaces with the complex logic already built into smart campaigns. We'll have to rethink our standard process for deploying campaigns in different regions now.

Please fix this Marketo!!!

[Dan_Stevens_]

Hi Jamye - with the December release, you can now directly clone programs across workspaces, without having to first clone to a local folder and move that folder.  Furthermore, the values can be left empty.  I did some limited testing on this and it appears to work.  But you do need to refresh your browser in order to see it in the destination workspace/folder.

[Jamye_Breidenba]

Thanks, Dan. Has anything changed with that process other being able to select the workspace in the "Clone" window? I tried cloning a program from one workspace to another and received numerous errors that the assets belonged to other "assets"... which is an odd one as I've never seen that error before. I have yet to make it work. I opened a ticket with support to see if they could assist but haven't heard back. Any ideas?

[Dan_Stevens_]

Jamye, one thing that hasn't changed is the need to ensure that none of your triggers, filters or flow steps reference assets that are only local to that workspace.  This has been a requirement for a few months now.  This is why we always take advantage of SHARED smart lists, templates (email and landing pages), snippets and segmentations.  You will need to remove them from the values (turning them into empty values) prior to moving/cloning to a different workspace.

[Jamye_Breidenba]

Thanks, Dan. After I saw your post that was my first step at resolving the issue, but still no luck. Hopefully I hear back from Marketo support soon as this is a business priority for us. We have a major campaign launching at the beginning of the year and our regional managers need access to the program for translation purposes in their workspaces.

Thanks so much for your help and presenting the idea. I hope you have a great holiday!

[Dan_Stevens_]

Unfortunately, this functionality appears to be broke again: Cloning programs across workspaces - be aware of a "fixed" capability that no longer works

Justin Cooperman​, who on the Product team should be notified of this (and re-open this idea)?