Filter for "Currently Exists in SFDC"

0 Likes

Filter for "Currently Exists in SFDC"

When a Lead or Contact is deleted from Salesforce, Marketo still maintains the SFDC ID and SFDC Type, even though that record has been deleted from Salesforce.  I think we need a better way to filter on Leads who currently exist in Salesforce.

It's possible that someone could be deleted from Salesforce, "SFDC is Deleted" would be set to true, and then that Lead syncs back to Salesforce.... "SFDC is Deleted" would still be true in this case.

A filter for "Currently Exists in SFDC" would be ideal to get around these nuances.
6 Comments
Anonymous
Not applicable
As a work around, you could use a Not Data Value Changed filter on the  SFDC is Deleted field with a "New Value is true" constraint.  This would identify all lead records that have never been deleted in SFDC, whether they were synched back and added to SFDC or not.
Anonymous
Not applicable
Thanks, good suggestion.

This does leave room for error though, considering that some leads can be deleted from SFDC and synched back with SFDC is Deleted  = to true.... they will slip through this filter still.
Anonymous
Not applicable
I may not be understanding what you are trying to accomplish.  Are you trying to prevent leads that have been deleted in Salesforce from being synched back to Salesforce and a new Lead record being created?
Anonymous
Not applicable
Trying to do a mass update on a particular field for all Leads / Contacts that currently exist in Salesforce. 

I don't want to sync Leads / Contacts that have been deleted from Salesforce back to Salesforce.
Anonymous
Not applicable
I reread your original post and you indicated that after a lead is deleted, the SFDC is Deleted field is set to true, which is correct, but then you indicated that if the deleted lead is synched back to SFDC, the SFDC is Deleted field value doesn't change.  I have not observed this behavior.  All the deleted leads that were subsequently synched back to SFDC had their SFDC is Deleted field set to false.  Can you reproduce this behavior?
kh-lschutte
Community Manager
Status changed to: Already have it