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!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Netsuite ignoring the date you set, sets its own
I've got a custom record type that has some date fields. Netsuite is intermittently ignoring the date that I am attempting to set and, without throwing an error of any kind, changing the value that I am attempting to set. Has anyone ever experienced this?
Example: I'm pulling the 'trandate' from a transaction record (itemfulfillment). I'm writing it to one of the date fields on this custom record. Sometimes it takes what I provided (e.g. 12/11/2013). Sometimes it ends up 1 day off (12/12/2013, for example). Sometimes it's 5 days off (12/16/2013). I know my values are correct, as I'm logging them and verifying in the script logs before I write to the date field. Yet I see in the resulting custom record that gets created that the value is incorrect.