ANS-1742 · WEB SERVICES & INTEGRATIONS
How to Reconcile Time Zones for Netsuite Records in Talend Integrations
The discrepancy occurs because Netsuite stores times in a specific time zone, while Talend's getCreatedDate function may interpret it differently, often converting to a local or system default time zone.
Short answer
When retrieving Netsuite record creation dates using Talend's getCreatedDate function, a time zone discrepancy may occur. For instance, a record created at 5 PM in Netsuite might appear as 8 PM EDT in Talend. This is due to differing time zone interpretations between Netsuite and Talend, requiring users to account for this offset in integrations.
Scenario
A common issue arises when integrating Netsuite data with external systems like Talend. Specifically, if a record is created in Netsuite at 5 PM, and its creation timestamp is then extracted using the getCreatedDate function in Talend, the retrieved time might show as 8 PM EDT. This three-hour difference highlights a time zone interpretation challenge between the two platforms.
Solution
The time zone issue observed occurs when a record is created in Netsuite at a specific time, such as 5 PM, and then its creation date is retrieved using the getCreatedDate function in Talend. The time returned by Talend, for example, 8 PM EDT, reflects a difference in time zone interpretation. This behavior indicates that the getCreatedDate function is applying a different time zone offset compared to the time zone in which the Netsuite record was initially created or displayed. Users should account for this consistent time zone discrepancy when integrating Netsuite data with Talend.
Expert NetSuite Support
Need help with this NetSuite issue?
Web Services & Integrations consulting and configuration support