SOLVED

Inconsistencies in the way SFDC ID can be used?

Go to solution
Highlighted

Inconsistencies in the way SFDC ID can be used?

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

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

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.

View solution in original post

9 REPLIES 9
Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

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.

View solution in original post

Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

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

Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

A few ideas to vote for on this:

-Greg 

Highlighted
Level 8 - Champion Alumni

Re: Inconsistencies in the way SFDC ID can be used?

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

Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

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

Highlighted
Level 8 - Champion Alumni

Re: Inconsistencies in the way SFDC ID can be used?

Right I see.

I think then the only way right now is a Delete Lead API call, as there you can select by Marketo ID? (Presumably you have that Marketo ID for the leads you want to remove, as you have identified in SFDC which leads you wish to stop synching and you can identify the Marketo ID of those.)

I know it would be nicer to run a smart campaign in the interface, just curious if this is what you did to solve for it.

Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

In fact, we will be using another Unique ID that we happen to have and that is a salesforce field.

But the REST API could indeed be a workaround. Thx.

-Greg

Highlighted
Level 10 - Community Moderator

Re: Inconsistencies in the way SFDC ID can be used?

FYI (since the thread is resuscitated) you can mirror the SFDC Id to another custom field via webhook.

mirrorOfSfdcId = {{lead.SFDC Id}}

Highlighted

Re: Inconsistencies in the way SFDC ID can be used?

Another scenario is when you want to select a bunch of records that match particular SFDC records, particularly when you have duplicates and you need to make sure that you update the correct record.  I have seen this requirement in many of my clients' Marketo instances.

- Erica