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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
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!
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!
Need to remove department from Subsidiary A, but maintain the department in Subsidiary B
Hello,
Our issue is we need to remove departments from subsidiaries, so they are not mistakenly coded on transactions. However we cannot remove the departments from the subsidiaries, due to this error message:
Setup > Company > Department > Edit Department > Removing subsidiary throws error message: You cannot remove subsidiary XXX because this record is used on a transaction for subsidiary XXX
Suite answers suggests:
A. Delete all the associated transactions in the saved search created above
B. Inactivate the department and then create a new one so this will not be associated with previous transactions.
Option A is not viable for us as it would require opening closed periods (etc.)
0