Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Classification Defaults - Best Practice
What is considered best practice for defaulting and controlling classifications on transactions? We've recently added some new physical warehouse locations and have noticed some issues cropping up where an item will be correctly set up, yet the transaction defaults header and line-level location incorrectly on quotes, sales orders, and other transactions. We do not want the end user to have to manually check this, as this adds time and room for error.
Right now, some roles have segment restrictions placed upon them (i.e. Location - none -default to own). This seems to be the culprit of our current woes.
3