Make it possible to create assets and campaign in a program folder

[Grégoire_Miche2]

There  is an annoying bug that has been there for quite a while : Create a program and, within that program, a couple of folders. Select one of these folders and right click --> "New Local Asset". Select any asset type you want, fill out the dialog and save. Guess what, : your new asset IS NOT in the folder, it's in the program root.

I do not know how many programs are in Marketo instances all around the world and how many assets where created. I would bet for millions. So millions of seconds where lost dragging and dropping the asset in its folder and thousands of people every day are grumbling about this bug 🙂

Dear Marketo Team, could you please have this fixed :-)??

[Dan_Stevens_]

Yes, this has been an annoyance for us for years now!  Especially in our environment where we have over 1,500 programs - and our typical program structure is as follows:

PROGRAM

[Assets folder]

- emails

- landing pages

- forms

[Campaign Flows folder]

- smart campaigns

[Reports folder]

- reports

Here are the existing ideas - I would vote on these rather than create a third idea related to the same topic (especially since Marketo hasn't found a way to merge related ideas into one, in the new community):

  (for some reason, it's marked as "already have it" - which is certainly not the case - can this changed back to another status Scott K. Wilder

[Grégoire_Miche2]

Duplicate with this one :

[Anonymous]

Thank you for the feedback on this one. I will see when we can push a patch for this.

[Grégoire_Miche2]

Hi Frank Passantino​,

Thx, Keep us posted

-Greg

[Dan_Stevens_]

Frank Passantino​ - any update on this?

[Anonymous]

According to this duplicate from 2013, status is "Working on this right now" - who knows from when. Anyway, this seems like it should be a fairly straightforward fix, surprised it's taking so long, as it's a clear bug.

Frank Passantino​ come to our rescue!

[Anonymous]

Ryan, this has been undesirable behavior for quite sometime, but we are working on a fix for it this year!

[Anonymous]

It's a year later... any update on this?

[Dan_Stevens_]

I suspect this fix will finally be included when the new user interface is released in 2018.

[Grégoire_Miche2]

Hi Dan,

yes, this is typically the kind of things that will have to wait for the new interface.

-Greg