Loading

Account Engagement fields displaying unexpected values when synced with Salesforce Date and Time fields

Publiceringsdatum: Sep 30, 2025
Beskrivning
Salesforce customers attempting to sync a Salesforce Date/Time type field to Account Engagement may see differences between how field data is presented in the mapped Account Engagement fields. 

Example 1
Differing dates:
Salesforce Date/Time field value: "1/29/2017 11:00 PM"  (viewing user in EST timezone)
Account Engagement Date type field value: "1/30/2017" 

Example 2
Different timestamp formatting:
Salesforce Date/Time field value: "1/29/2017 11:00 PM" (viewing user in UTC timezone)
​Account Engagement Text type field value: "2016-01-29T 23:00:00.000Z"
Lösning

Date/Time database values in Salesforce are stored in a standardized format in the UTC timezone. Salesforce users have the ability to set their locale and timezone settings, which converts the standard Date/Time field values into their respective timezones when viewing a Salesforce record. 

However, Account Engagement fields will sync down the standardized UTC timestamps, regardless of individual user timezone/locale settings in Account Engagement or Salesforce.

To avoid unexpected values syncing to Account Engagement, customers can instead opt to map a Salesforce Date type field (rather than a Date/Time field) to an Account Engagement Date or Text type field.


Alternately, users may create a Salesforce formula field to transform the date format. Since formula fields do not trigger an update to Account Engagement, the recommendation would be to map both the original field and the custom formula field in order to trigger the sync.


 

Knowledge-artikelnummer

000382502

 
Laddar
Salesforce Help | Article