Delete Lead vs. Delete Lead from SFDC Flow Steps | Community
Skip to main content
February 23, 2016
Solved

Delete Lead vs. Delete Lead from SFDC Flow Steps

  • February 23, 2016
  • 1 reply
  • 1386 views

This seems to me like a very simple question, but will these two flow steps effectively complete the same task? Also, wouldn't the second step ~also~ permanently delete the lead from Marketo? Why isn't that warning displayed here, too?

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 Diederik_Marte4

Well with both options set to True, it would achieve the same. But in some cases you might only want to delete it in Marketo or Salesforce only (e.g. it shouldn't have been dispatched to salesforce yet). Delete lead is Marketo native, whilst Delete from salesforce is extra due to the integration. The warning message isn't there as Marketo doesn't know if deleting it from salesforce, actually will permanently delete it, as there might be all kinds of backup procedures installed by the Salesforce admin (p.s. deleted leads Always end up in a waste bin first for a while in Salesforce). I hope this helps.

1 reply

Diederik_Marte4
Diederik_Marte4Accepted solution
New Participant
February 23, 2016

Well with both options set to True, it would achieve the same. But in some cases you might only want to delete it in Marketo or Salesforce only (e.g. it shouldn't have been dispatched to salesforce yet). Delete lead is Marketo native, whilst Delete from salesforce is extra due to the integration. The warning message isn't there as Marketo doesn't know if deleting it from salesforce, actually will permanently delete it, as there might be all kinds of backup procedures installed by the Salesforce admin (p.s. deleted leads Always end up in a waste bin first for a while in Salesforce). I hope this helps.

6x Marketo Champion | Marketo Certified Solutions Architect (MCSA) | Marketo User Group Leader | International Speaker on Marketing Technology
February 25, 2016

Thanks, Diederik!