Dave-Silva

That's what I figured/hoped. I just couldn't find any official documentation indicating that.Perhaps someone from Adobe can provide a link to documentation that describes that behaviour?

Huh. I tried it again and it worked. Not sure what I did wrong previously. Thanks!

Yeah @Miray, I'm not sure this would solve the problem, which is that ultimately we have situations where we want to advance a lead status/lifecycle in SF (Sales team actions), and other times where it is Marketo driven (scoring). Even decoupling the status from lifecycle, there are still the two sy...

The sync error doesn't seem to ever get resolved automatically -- I need to intervene and update Marketo's value to what's in Salesforce to allow the sync to resume. Pardot used to provide an option for conflicts, where the value in SF (or Pardot) could be chosen to overwrite the other, but I'm not...

Yes, Lead Status is what I'm referring to -- it's in the subject 🙂 The problem is, I believe, that Marketo isn't "aware" of the new status yet. So I can't restrict setting the Lead Status to MQL if it's "Working", because it's only "Working" in SF. So:1. Lead is created in Marketo with a status of...

To be clear, these aren't campaign statuses -- it's the our core Lead Status field. So these aren't "Change Status in SFDC Campaign" flows, but rather simply field value updates, which are used to drive our lead lifecycle progression. So it should be comparable to someone updating the value in Marke...

Below is the script I'm using. It was just to test a manual association. //////// ASSOCIATE WEB ACTIVITY TO LEAD ////////const associateWebActivityToLead = async (leadId, cookieValue) => { const marketoInstance = 'https://█████.mktorest.com'; const clientId = '█████'; const clientSecret = '█████'...

Please see my response to Miray. The progressions are symmetrical, though we don't have them tied to a program status. So it seems to be an issue with timing between when a rep updates the status in SF and a sync is occurring from Marketo with a competing "previous" value in the progression.

We use smart campaigns to set change the status, but don't have it tied to Program StatusesWe have other fields involved, but that is the only one involved with a validation ruleYes, "Working" exists in both systems and is not a problem for most records. However, several records each week encounter ...