How do we prevent a date from converting to UTC in the netsuite.com connector? We have a stored date that is stored as 7-31-2024 but is being converted to 8-1-2024 when it goes to the data warehouse.

AI generated answer (using internal Slack threads):

The issue you're experiencing is due to the way NetSuite handles date and time. When you're setting a date in NetSuite, it's stored as a datetime value at midnight in the timezone set in the UI. When this date is retrieved, it's converted to Pacific Standard Time (PST) or Pacific Daylight Time (PDT), depending on the time of the year. This conversion can cause the date to shift if the timezone of the user retrieving the data is ahead of PST/PDT. For example, if you're storing a date as "7-31-2024" and your timezone is ahead of PST/PDT, when this date is converted to PST/PDT, it could become "8-1-2024". To prevent this from happening, you need to account for the timezone difference when setting the date. One way to do this is to add the timezone offset to the date when setting it. For example, if you're in Central European Time (CET), which is typically ahead of PST/PDT by 8 or 9 hours, you could set the date as "7-31-2024T080000.000+02:00". This will ensure that when the date is converted to PST/PDT, it remains as "7-31-2024". However, this solution may not work for all hours of the day due to the difference in daylight saving time rules between timezones. Therefore, you may need to adjust the offset depending on the time of the year. Please note that this solution assumes that the timezone of the user retrieving the data is consistent. If you have users in different timezones retrieving the data, you may need to implement additional logic to handle the timezone conversion. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******