When a lead with an interesting moment is cloned in SFDC, the interesting moment description will transfer to the new lead. However, there is no record in Marketo of this new lead having an interesting moment via a flow step, they simply just have an interesting moment description. Is it possible to "NULL" an interesting moment when a lead is created in SFDC? I won't be able to filter by "had interesting moment" because the lead didn't have one, so I will just need to NULL the interesting moment for all new leads created via SFDC because they couldn't have had an interesting moment if they were just created (in our instance, for example).
Any thoughts?
Solved! Go to Solution.
Hi Devraj,
My writing above was not correct neither clear. Sorry, it should have read:
Last Interesting moment Desc, Date, Source and Type are system maintained, and cannot be updated with a "Change Data Value" flow step in Marketo.
I would try to create a workflow that does the job in salesforce and that would trigger on lead creation, only when the creating user is NOT the Marketo user. Not sure it works, but worth a try.
-Greg
Hi Devraj,
Last Interesting moment Desc, Date, Source and Type are system maintained, and cannot be updated with a "Change Data Value" flow step in SFDC.
I would try to create a workflow that does the job and that would trigger on lead creation, only when the creating user is NOT the Marketo user. Not sure it works, but worth a try.
-Greg
I also tried to run a interesting moment flow step for the lead with the type: NULL and description: NULL thinking it would nullify whatever value was in there. But it actually put "NULL" in the description, so that won't work.
Hi Devraj,
My writing above was not correct neither clear. Sorry, it should have read:
Last Interesting moment Desc, Date, Source and Type are system maintained, and cannot be updated with a "Change Data Value" flow step in Marketo.
I would try to create a workflow that does the job in salesforce and that would trigger on lead creation, only when the creating user is NOT the Marketo user. Not sure it works, but worth a try.
-Greg
Appreciate it, thanks Greg.