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.
Ability to create 'Contact Select' like 'Bill To Select'?
I've searched the community and didn't find a specific request like this one.
Does anyone know of a way to create a 'Contact Select' type of input on a transaction form that would be very similar to the 'Bill To Select' functionality within the Address section? Once the entity/account has been chosen for the transaction, the 'Bill To Select' dropdown menu only lists addresses associated with that entity, with the primary as the default.
I would like to offer the same functionality to the end users to select the correct contact from the entity as the lead contact for that transaction. The current implementation of contact within the history subtab is not very robust. If a primary contact is specified, that contact will be prepopulated in the history subtab. However, there isn't a way to choose one of the other contacts in the entity. Also, from my testing, any contact newly entered in this area will only be associated to the transaction not the entity. This could lead to orphaned contacts across transaction records.