Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
handling date/ time in suite script
We are fairly new to NetSuite, but old hands at CRM. We have an event-driven environment, and when those events happen needs to be logged in the NetSuite system.
When accessing date/ time fields through the UI, or defaulting the fields, it is possible to say to the system that an event happened 'now', and that is modified to be 'now' in the local timezone. However, if a suite script places a call to Date(), it gets the server time, which isn't our timezone, and if it writes that value into the date field, the time shows as server time, not local time.
0