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.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
How best to handle scripted dates in International implementations
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.