Option to clone asset/campaign into same/existing program

[Dan_Stevens_]

Currently when you want to clone an asset (e.g., local email) or smart campaign within the same folder, you're forced to select "Programs..." and then search for the program, just as if you wanted to clone it to another program within Marketing Activities.  This becomes tedious when you have hundreds of programs.  It would be so much easier if there was an option within the "clone to" field to include "Existing Program" (along with "Programs..." and "Folders...").

[David_Gallaghe2]

I dig the idea! I would aslo suggest adding folder drop down for the selected program so we can drop the cloned item directly where it needs to go inside the program without needing to move it later.

[Anonymous]

When I clone an asset it defaults to the current program automatically. Is that not what you're seeing?

[Dan_Stevens_]

Not for me.  Here's what I see when cloning different types of assets/campaigns within a Program:

[Anonymous]

Weird. My instance works fine. If you haven't, can you open a case with support? They can capture your info and file the bug.

If that's too troublesome, you can just email me your subscription name, your username, and a link to the assets and I'll look myself. (I'm erik@marketo.com)

[Anonymous]

Hi Dan,

I just responded to this case. Take a look and get back to me via the case notes. 

Thanks,
Chris

[Dan_Stevens_]

Hi Chris - unfortunatey, your suggestion didn't work.  I provided steps to reproduce within the support ticket.

[Anonymous]

Thanks Dan. Looks to be a mixed experience, based on the program you select. I'm going to find a few more "failing" examples and escalate this to Engineering. 

Regards,
Chris

[Dan_Stevens_]

So I finally received a response from Support and they've determined that this behavior is "by design" and not a bug.  Their response is below.  So the "Idea" I submitted is still very much desired.

[RESPONSE FROM SUPPORT]:

Engineering has determined that this is by design, and has nothing to do with the specific programs you mentioned.

If the local asset is under the program, the program will pre-populate when being cloned. If the local asset is in a sub folder under the program, the program will not pre-populate.

We did find one minor issue. When a local asset is moved, its owner asset id is not changed unless the page is refreshed.

When a local asset is cloned, we will wipe out the clone's parent program info but leave the owner asset id the same as the origin. If the owner asset is the same as the parent program, the parent program will pre-populate; otherwise, it won't.

if (cloneFromAsset) {
asset = cloneFromAsset.copy();

// reset fields that should not be propagated to cloned asset
asset.set({
assetId: null,
programAssetId: null,
name: null,
description: null,
allowedZoneIds: [
asset.get('zoneId')
],
isArchived: false
});

I realize this isn't the answer you were looking for. However, it appears that the behavior you described is not a bug, and no changes to that will be made.

Please let me know if you have any further questions regarding this case.

Thanks,
Chris

[Anonymous]

.

[Anonymous]

Hi Dan,

This is a very confusing answer you got, sorry about that. Even if it's not a bug, doesn't mean we won't change it. I'll look up the case and see.

-Erik