I am observing the following behavior :
Are you observing the same ?
Is this an expected behavior ?
Then I have pushed the test a little further : I updated the lead source field again in Marketo (with a more recent value than in SFDC). On following sync, SFDC was updated with the same value as Marketo.
As long as the field isn't critical, it won't break the rest of the sync, just that value. It would be better to lock the field in SFDC from manual (casual) changes and then uncheck the field block in Marketo (although that's not necessary).
Hi @Josh & Sanford,
Sure, yet, blocking a field only when it contains a value is not easy in salesforce. It can be done only with a validation rule, you will have to still authorize some users, which will require a complex validation rule and yet some cases will be complex to handle in case you still need to update it.
The behavior, IMHO, would be more consistent if Marketo was also enforcing SFDC to keep the unchanged value.