Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
nlapiStringToDate
Can someone please help me with my understanding of nlapiStringToDate. In particular using a format datetimetz.
The documentation says that using a format of datetimetz when calling nlapiStringToDate returns the date in the time zone of the user's netsuite preference not the browser.
For example nlapiStringToDate('3/22/2013 10:00:00 AM','datetimetz') on the client side results in a date object with the timezone of the machine not the user preference.
On the server side the time zone of the resulting date object is always GMT -8 regardless of the user's netsuite time zone preference.
***UPDATE If the value is retrieved from a custom field of type datetime, the time portion of the resulting date is the correct time in the users timezone as set in their preferences but the date object is in the time zone of the server. After reading more about the javascript date object this seems by design.