megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Don't miss out on our Question of the Week! You only have until tomorrow, March 26, 2026, 2:00PM ET to comment your answers.

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!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

How best to handle scripted dates in International implementations

edited Dec 2, 2019 6:30PM in SuiteCloud / Customization 2 comments

Hi,

I deployed a script a few weeks ago that automatically sets a date in a custom date field in a custom record.

Our European employees are now causing this script to fire and it looks like their local preferences for date format is causing a problem.

I am setting the date as mm/dd/yyyy.  Their preferences are dd/mm/yyyy.  When the record is saved from the script it throws the following error:

"You have entered an Invalid Field Value 9/14/2007 for the following field: custrecord_replacement_sent"

Can anyone suggest an easy way to determine and set the appropriate date format?  I sure hate the thought of having to do another lookup to a user's record to determine what their date preference is set to since that seems like a lot of overhead.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders