Your Achievements
Level 1
0% to
Level 2
Next /
to gain points, level up, and earn exciting badges like the new Applaud 5 BadgeLearn more!
View All BadgesSign in to view all badges
Open Alert Bar

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

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

Status: Open Ideas Submitted by Level 10 on ‎02-21-2017 10:13 AM
11 Comments (11 New)

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

4,264
11 Comments
Frank_Elley
Level 3
Level 3
‎02-21-2017 10:49 AM
‎02-21-2017 10:49 AM

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
Level 10
Level 10
‎02-22-2017 01:09 AM
‎02-22-2017 01:09 AM

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

Frank_Elley
Level 3
Level 3
‎02-22-2017 06:48 PM
‎02-22-2017 06:48 PM

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

Frank_Elley
Level 3
Level 3
‎03-06-2017 05:18 PM
‎03-06-2017 05:18 PM

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_
Level 10 - Champion Alumni
Level 10 - Champion Alumni
‎07-17-2017 08:07 AM
‎07-17-2017 08:07 AM

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
Level 10
Level 10
‎07-17-2017 01:53 PM
‎07-17-2017 01:53 PM

Hi Dan,

Done

-Greg

Erica_Harris2
Level 3
Level 3
‎08-21-2017 05:06 AM
‎08-21-2017 05:06 AM

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

Frank_Elley
Level 3
Level 3
‎08-24-2017 04:27 PM
‎08-24-2017 04:27 PM

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_
Level 10 - Champion Alumni
Level 10 - Champion Alumni
‎08-24-2017 04:42 PM
‎08-24-2017 04:42 PM

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
Level 10
Level 10
‎08-25-2017 04:09 AM
‎08-25-2017 04:09 AM

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

Home