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
Before Submit Function and Routing Rules - Not Playing Nice?
UG,
Here's an interesting issue I'm running into.
Background:
We have lead forms (built in NS) that prospective clients fill out and submit. I have a script that runs on all new Lead records during the before submit phase. Several of the fields on the form need to be translated so that they are NetSuite "friendly" and can be mapped to NS fields that exist. (these values come from a different database via some webservices)
Issue:
We have routing rules that route the new leads to reps based upon some of the values that are translated - which happens during the before submit phase. What I'm finding is that the lead records are being routed...funky. Sometimes they route correctly based on the translated values, and sometimes it looks like the lead is routed based on only some of the values - like not all of the fields were populated before the lead routing kicked in.