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
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.