Inconsistencies in the way SFDC ID can be used? | Community
Skip to main content
Grégoire_Miche2
Grégoire_Miche2
New Participant
June 23, 2016
Solved

Inconsistencies in the way SFDC ID can be used?

  • June 23, 2016
  • 2 replies
  • 3776 views

I observe an inconsistent behavior of the SFDC ID field:

  • It can be added to a view, displayed and exported
  • It can be used as a token in an asset

But

  • It cannot be used as a filter in a smart list...
  • It cannot be used as a token for the new value in a Change Data Value flow step
  • It cannot be used as the attribute in a "Data Value Changes" trigger not in a "Data Value Changed" filter

Tested this on a couple of instances with the same result.

Am I the only one to see this?

-Greg

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

Hi Gregoire,

The behavior you have observed is correct and is expected.  The Lead ID field in Marketo also has the same constraints - it can be viewed in a list and displayed as a token in an asset, but cannot be referenced in a Smart List or Flow Step.

2 replies

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
June 24, 2016

A few ideas to vote for on this:

​

​

-Greg 

Justin_Norris1
Justin_Norris1
New Participant
June 24, 2016

Hi Greg,

What are your use cases for wanting to filter by the SFDC lead ID? Trying to think of a scenario where this would be necessary.

Justin

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
June 24, 2016

Just after setting a sync filter. Suddenly, thousands of leads not longer sync, but there is no way to select them in Marketo (in order to delete them), especially if your database has some duplicates and therefore filtering by email address is not an option.

This is a real case: in a complex SI, some other software are pushing duplicates in SFDC by tens of thousands. After a while, and because suppressing them or merging them is not an option, we decide to set a sync filter and to have these duplicates not to sync, only one primary contact should sync. But how do we remove only the secondary contacts from Marketo and they are all identical?

I would love to have this idea implemented: or this one: ​, but none of them works.

-Greg

Roxann_McGlump1
Roxann_McGlump1Accepted solution
New Participant
June 23, 2016

Hi Gregoire,

The behavior you have observed is correct and is expected.  The Lead ID field in Marketo also has the same constraints - it can be viewed in a list and displayed as a token in an asset, but cannot be referenced in a Smart List or Flow Step.

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
June 24, 2016

Hi Roxann,

Thx. This is what I had figured out from the other instances, all of them behaving the same.

Does not really make sense though

And not convenient either.

-Greg

Terms & ConditionsAccessibility statement

Loading footer...