Formula/Look-Up/Reference SFDC Field Not Updating in Marketo | Community
Skip to main content
November 30, 2018

Formula/Look-Up/Reference SFDC Field Not Updating in Marketo

  • November 30, 2018
  • 3 replies
  • 4785 views

Issue

You are using a formula/look-up/reference field in Salesforce, the field is synced to Marketo, but you are not seeing updates sync from Salesforce to Marketo.

Solution


When a SFDC formula/look-up/reference field is updated, the SysModStamp does not update. The SysModStamp is how the sync knows which record (Marketo vs SFDC) is more up to date. You can think of the formula/look-up/reference field like a window to a different value. If the value inside the window changes, that does not queue the record up to be synced. But if the record is queued up to be synced due to another update made to the record, like changing first name, then the current value inside the window will sync down to Marketo.

 

To avoid this delay in updating, you may wish to replace the formula or lookup field with a string field that has the appropriate value written to it by a workflow. Updates to SFDC string fields will always update the SysModStamp and queue the sync to Marketo.

 

 


This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Jonathan_Wu
Level 3
November 30, 2018

Also resetting the watermark does not bring these values over.

Danny_Smith
December 17, 2018

What? The resolution is to not use Formula/Reference fields or just cross your fingers and hope that all your records are updating often enough that all field updates from Salesforce have made their way into Marketo somehow though a different, unrelated sync? This seems unacceptable for a $4.75bn company as Formula/Reference fields are essential to any org using Salesforce (which according to most makes up a majority of Marketo's customers).

SanfordWhiteman
Level 10
December 17, 2018

A company's valuation doesn't predict their ability to do miracles.

The records simply aren't marked as updated. There's nothing Marketo can do about this on their own. The underlying technical problem, however understandable, is on the SFDC side.

Note this is the way dynamic computed columns (= formulas) work in any database. A row is not abstractly considered "updated" unless a static column changes. Directly getting the computed column in a row will return the latest value on-the-fly, but knowing in advance which values would be updated if directly queried isn't possible.

Under some conditions (and not default configs) databases can automatically persist (= save) computations as the contributing data changes. This is equivalent to the recommendation in this article to save the data permanently to another field. Again, it's under control of the database. Not the application reading the database.