2 of 2 people found this helpful
the additional, forced sync, is not necessary.
I would look into the right model or some validation rules that prevent the update to the SFDC record.
Start with an attempt to update another field in Marketo on these records and check these other fields do sync.
Just adding to Greg's comment. I would also check the activity log to see if the record has synced/updated back to SFDC after the custom score value has changed.
If you find that there has been an update back to SFDC for that record then you would be looking at custom validation rules on SFDC that may be preventing this update from happening - as Greg mentioned.
Hope this helps!
I agree with Greg & Floyd. Another thought - and sorry if this is too obvious - I'm guessing this field is on the Lead and the Contact in SFDC. Are the two mapped together and did they sync down to Marketo as one field? Worth double-checking...
After some investigation, turns out the Marketo Integration User Permissions had been mistakenly overwritten to be read-only for the field. Lucky for me, I already had block field updates from SFDC Sync enabled for the field inside Marketo, so Marketo's data is still clean. We updated the permissions, forced a sync, and all looks good.
Appreciate all the insights. Good to know the forced sync is not necessary for sure, seems like it's just permissioning issues with our sync setup. I'm going to get a fully audit underway to avoid the issue moving forward.
That was my first take: look at the rights model...
Yea, I didn't think that would be the sources of the problem as I had already encountered THAT issue and had the permissions updated! Those permission changes were accidentally overwritten, causing the issue to occur again. Luckily this time around I had stopped the field updates from SFDC Sync so Marketo was nice and clean Not the case last time. Had to do tons of resetting as the degrade rate of the scores was all messed up. Appreciate your input as always!