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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly 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.
Strict validation
I can't remember if this was answered, but I do not see it anywhere in my searches.
The biggest issues we are having with our client right now is the input of phone numbers. On our end, phone numbers are not made to follow any format. It can be 12345678 or 1.234.5678, etc.
If we were to submit any kind of lead data with those formats, Netsuite errors out and drops the lead completely. Hence, we've resorted to creating a custom field for phone number, but the ideal is to have it be in the actual phone field.
In the version that's in beta right now to the customers (and I imagine it's what I've been working with since I got my sandbox account a month ago), I don't think I encountered that validation issue until I migrated my code to my client's instance, which is the production version.