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