Administration is the key(bunch) | Community
Skip to main content
Vikram_Ramesh
Vikram_Ramesh
Level 2
August 29, 2019
Question

Administration is the key(bunch)

  • August 29, 2019
  • 13 replies
  • 10245 views

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

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    13 replies

    Show previous replies
    Nicholas_Manojl
    Nicholas_Manojl
    Level 8
    October 9, 2019

    - Developers require Admin access to access the Custom Objects/Custom Activities consoles. Ideally, this wouldn't be necessary. 

      Vikram_Ramesh
      Vikram_RameshAuthor
      Level 2
      October 16, 2019

      hello @Nicholas Manojlovic‌,

      are you suggesting that there needs to be an export of this information or extending the access to other users on the same page?Just trying to understand and then check for its feasibility here.

      Regards,

      Vikram R

      email: Vikram.ramesh@adobe.com

      phone: +91 988 607 4356

      Vikram Ramesh
      Nicholas_Manojl
      Nicholas_Manojl
      Level 8
      October 16, 2019

      Hi Vikram - turns out my suggestion is on the 'we already have it!' list. I was unaware we could create a user role with defined Admin privileges. 

      Amit_Jain
      Community Advisor
      Amit_JainCommunity Advisor
      Community Advisor
      November 1, 2019

      Some of these might already be pointed out but here is my take:

      • SFDC Field sync: As of now, Marketo sync all the fields visible to marketo user in SFDC automatically and if we already have a similar field existed in Marketo, it creates a duplicate. We have to go to Marketo support to merge those fields. It would be ideal to let admin which SFDC field needs to be sync with Marketo and merge with existing field, if needed.
      • Field Management:
        • Right now, it shows the field dependency in a list and if it's being used in lot of assets, we have a "load more" option. It doesn't show the number of assets it's being used. It would be really nice to have a feature to export all the field dependencies and also a summary table that will show the number of assets per asset type like forms, smart lists etc.
        • Delete the fields instead of hiding
        • Let Admin merge the fields if needed
      • Custom Objects: Custom objects are really useful at times but it comes with an overhead of developing something outside marketo to feed the data. It will be really really cool to allow custom objects to be updated right from smart campaigns. It will seriously save a lot of time developing some solution using custom object.
      • SFDC-Marketo sync: Today, it just shows the last sync time or if the sync is in progress. Would be nice to have some more details on the previous sync logs and also what is current being synced between the systems and how many records, expected sync cycle completion time. Also, it would be nice to have a button to start sync cycle immediately.
      Josh_Hill13
      Josh_Hill13
      Level 10
      November 1, 2019

      Amit Jain wrote:

      Some of these might already be pointed out but here is my take:

          
      • SFDC Field sync: As of now, Marketo sync all the fields visible to marketo user in SFDC automatically and if we already have a similar field existed in Marketo, it creates a duplicate. We have to go to Marketo support to merge those fields. It would be ideal to let admin which SFDC field needs to be sync with Marketo and merge with existing field, if needed.
        •   
          Yes, orphaned fields are a problem and they typically appear based on their object in this case. Sometimes it's helpful, sometimes not:
            Opt In (L) (C) or (A) if this happens.
              But sometimes it's just on one object, sometimes not. The best thing to do in this situation is to ask Support to help you merge the fields. The challenge is to do this as soon as you notice this, or work with them BEFORE you create the field in SFDC. They can merge the fields, but it does destroy data if you don't do it right.
            Amit_Jain
            Community Advisor
            Amit_JainCommunity Advisor
            Community Advisor
            November 6, 2019

            Hi Josh,

            Thanks for the suggestion but the problem is that before merging the fields, you have to remove all the dependencies and then you have to update it back after the merging. Sometimes, this become a tedious exercise and kind of impossible to do it manually.

            Casey_Grimes2
            Casey_Grimes2
            Level 10
            November 6, 2019

            So, I'd actually like to advocate for two items that were previously on the Marketo roadmap but seem to have gone missing: Field Metadata API and User Provisioning API. The two most common things I do when in the Admin section are either creating fields or handling users—and the idea behind both of these APIs were to solve common pain points around both.

            By having a Field Metadata API, third-party integrations could add/update fields as needed rather than forcing the end user to enter fields by hand. Likewise, the ability to mass hide outdated fields would be a big boon--I once spent nearly 20 hours hiding ~700 fields from a client instance, and I could have just as easily done that in 20 minutes with an API call that would let me review fields and then post an update to hide them from UI. 

            Likewise, with most enterprises onboarding/offboarding marketing employees, there's automation for adding and removing Exchange inboxes, Salesforce users, HR software logins... but no way to hook Marketo into this setup. As such, you're stuck adding and removing users manually, which is a pain. There's no reason a user API couldn't just hook into Workday or other HR systems to make this part of the onboard/offboard process.

            These things don't sound cool or appealing, so they tend to die on the vine--but the convenience they afford when given context makes them worth it.

              Vikram_Ramesh
              Vikram_RameshAuthor
              Level 2
              November 18, 2019

              Hello Courtney,

              you certainly seem to know your way around APIs well. I really appreciate that and your suggestions too.

              I would like to explore why was this dropped off from the roadmap from my sources. 

              If you don't mind, I'd like to learn from you on your specific asks on these APIs. 

              The possibilities that you've pointed out does sound lucrative for Admins. 

              Regards,

              Vikram R

              email: Vikram.ramesh@adobe.com

              phone: +91 988 607 4356

              Vikram Ramesh
              Terms & ConditionsAccessibility statement

              Loading footer...