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.
Custom Record or extend existing records?
I have two entities that I need to model in NetSuite:
[LIST]
[*]Physician (basically a contact with a few extra fields)
[*]Insurance Company (very basic requirements; address, contacts, name and some child records)[/LIST]I'm REALLY struggling with whether I should continue to use custom records for these entities or if I should abandon that and extend a built in record (Customer or Contact) to model physicians and ins. co.
I've found myself adding fields like:
[LIST]
[*]Address 1
[*]Address 2
[*]State
[*]Contacts (child records)
[*]Phone
[*]Fax
[*]etc[/LIST]
Obviously these are all fields that exist on the built in records.
The main reason I'm NOT using built in records is that it's very difficult to differentiate a Physician (represented by a Customer record) from a regular customer in the UI. The same is true for Insurance Companies. My users will be VERY confused if they try to create a new Physician and the form says "Customer".
Steve Klett | Senior Developer
NetValue Technology
