Date discrepancy for some user time zones in Eloqua when retrieving date-only fields from SFDC CRM (
With the arrival of Eloqua release 18D (November 16 - 17, 2018), a change will be made to correct an issue related to importing strict date fields from salesforce.com via Eloqua’s native salesforce.com integration. Prior to the 18D release, customers with the date field mapped may notice in the values imported from salesforce.com strict date field (date only, not date/time) being incorrect by one day.
For customers using Eloqua’s native salesforce.com integration, and have any date fields mapped, a change is being introduced with the arrival of the 18D Release that will correct an issue that resulted in day values as being incorrect by one day. Currently date-only field values being retrieved from salesforce.com are shown and evaluated in Eloqua as the prior day. This is due to a time stamp that is applied to the field value during import to Eloqua.