Create a way to differentiate users with the same names for SFDC or MSD assignment | Community
Skip to main content
Grégoire_Miche2
Grégoire_Miche2
Level 10
February 21, 2017
New

Create a way to differentiate users with the same names for SFDC or MSD assignment

  • February 21, 2017
  • 6 replies
  • 6407 views

The way the "Sync lead to SFDC" or the "Change Owner" flow steps work can be quite dangerous if multiple SFDC users in the organisation have the same First and last names. This is the same in the "Sync lead to Microsoft" flow step.

It should be possible to differentiate them with their CRM Username or nickname.

-Greg

    6 replies

    F
    Frank_Elley
    Level 3
    February 21, 2017

    Hi Gregoire. I just added something to similar to Product Discussion ... probably should have put it in Ideas here. Important point here is that neither Username nor Alias is guaranteed to be unique, especially across different user types (partners, community users, etc.). This may be an example of poor/odd/greedy user licensing models on the part of SFDC, but we can't change that. This should be chained to the other idea about enabling token use for the sync lead and change owner flow actions. A token for "enterprise sales rep for the west" linked to an explicit SFDC ID would make updating complex routings so much easier.

    Grégoire_Miche2
    Grégoire_Miche2Author
    Level 10
    February 22, 2017

    Hi Frank

    Fully agreeing on this. Have you reviewed the various ideas listed here: Marketo / salesforce integration needs a serious overhaul, don't you "sync"?

    -Greg

    F
    Frank_Elley
    Level 3
    February 23, 2017

    Yup ... just went through it again and voted up some more painful and frustrating issues. Thanks for so diligently curating this list!

    F
    Frank_Elley
    Level 3
    March 7, 2017

    And ... one thing to note here, lest it be forgotten. This isn't an idea for a product feature or even an enhancement. This is one way to fix a bug that makes a very fundamental feature unusable for large enterprises.

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    July 17, 2017

    We're dealing with this issue for a couple of users today.  Support asked me to create an Idea.  I shared this one with them.  Would be great if this could be generalized to cover all CRM systems.

    Grégoire_Miche2
    Grégoire_Miche2Author
    Level 10
    July 17, 2017

    Hi Dan,

    Done

    -Greg

      E
      Erica_Harris2
      Level 3
      August 21, 2017

      Is there a workaround? It seems that even if you edit the name in SFDC to be unique, Marketo does not re-read it. I'm dealing with the same problem, I agree that it is a bug, not an enhancement!

      By the way this applies to assigning a task, not just sync or change owner.

      - Erica

      F
      Frank_Elley
      Level 3
      August 24, 2017

      Working with Marketo support, we came up with this workaround: We added a custom field to our SFDC user accounts: Sync to Marketo? Which does what it implies: in our instance, they introduced a rule to sync only user account records that were flagged this way. We then deleted (thousands) of records from their cache that weren't flagged in this way.

      Dan_Stevens_
      Dan_Stevens_
      Level 10
      August 24, 2017

      We're using the custom sync filter today in our instance (not for this specific use case).  How does this solve the issue of having a "john smith" in the US and and "john smith" in the UK as users who would be assigned leads from Marketo?

      Grégoire_Miche2
      Grégoire_Miche2Author
      Level 10
      August 25, 2017

      Hi Dan,

      It does not It would only be relevant if John Smith in the US was supposed to receive leads and John Smith in the UK was not.

      -Greg

      K
      kh-lschutte
      February 6, 2020
      No text available
      Terms & ConditionsAccessibility statement

      Loading footer...