Administration is the key(bunch)

[Vikram_Ramesh]

Through this post I intend to shout out to all admins in the community (and elsewhere). Admin is really like the key-bunch which could unlock/lock and maintain all the goodies Marketo has to offer.

Like every other component, once in a while we do need provide healing touches to the segments which hasn't been working so well. Also, the ones that are working well could use a performance boost. So, here's what I'd want to know from you:

1. What according to you is the single most disliked feature of admin?
2. What is the most used functionality of admin for you?
3. Are there any commonly used workarounds which you'd like admin to cater for?
4. If we were to provide an export feature of configurations, what details would you like in that "data take-out"?

Any thoughts/comments/feedback/criticism (positive or negative) revolving around Admin are greatly welcomed. Please feel free to reach out to me to discuss some of the ideas you may have. 

Looking forward to hear from you.

Thanks,

Vikram R

email: Vikram.ramesh@adobe.com

phone: +91 988 607 4356

[Vikram_Ramesh]

I hear you. it does open in the same page. while dealing with a field which is heavily used, its strenuous to get the tasks done. a very valid suggestion indeed. Thanks again

[Maria_Karlsson1]

Hi Vikram, I totally echo Grants points here both about Salesforce sync and Field admin as we also have a very old instance and have been through a lot of rounds of having to remove fields from hundreds of assets one by one before being able to rename or hide this field. I am ok with keeping api name the same just like Salesforces does but we sometimes need to be able to rename the friendly label for the users as some fields don't make sense at all. Also if you want to do an audit of which fields have what setting, what the field is blocked from and if it's synced to salesforce you can export one list. The field list export only gives the field names and API names. If there could be added columns for all the settings that would be great!

[Vikram_Ramesh]

I am learning that, dealing with redundant fields are a pain point for many. Either reuse them or deleting them should be the ideal way to deal with. I am just analysing repercussions (if any) in deleting as well as renaming an existing field. 

Also on the export, that's a nice suggestion. Seems fairly straight forward too. 

Thanks again Maria for these inputs  I really appreciate it!

Regards,

Vikram R

[Amy_Goldfine]

Our SFDC Admin sometimes renames the friendly label of a field, and then it has a different name in Marketo, which can be really confusing. They changed "Lead Status Reason" to "Closed Status Reason" and I have to think about which is the "real" (SFDC) name when talking to people or writing documentation.  

[Meg_Stout]

Yes to renaming fields! That would be hugely helpful. 

[Josh_Hill13]

Are you taking a product survey for Marketo? I'm confused what you want to learn.

[Vikram_Ramesh]

Hello Josh,

Yes, in a way.

I am the product owner for Admin related features. I am hoping to gather feedback to strengthen my case for some enhancements. please let me know if we can discuss more

Thanks,

Vikram R