Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
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.