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!
Loss of field data "by design"
NetSuite is claiming the bug below is "as designed" and is an enhancement. Check out their suite answer below:
https://netsuite.custhelp.com/app/answers/detail/a_id/18294
So:
1) You have a transaction column field on a Quote with data. Lets call this field "My extremely important checkbox". It's checked right now.
2) Create a Sales Order from that Quote.
3) If the default FORM for the user creating the Sales Order doesn't have "My extremely important checkbox" set to show on the form. Data is lost, checkbox is now false.
NetSuite is claiming this is as expected and by design. If that was the case, why would this only happen on transaction column fields and not transaction body fields?
0