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
Document Version History.
Hi Folks,
I was wondering if anyone has implemented on the transaction side of things document version history and how they did it. In regards to Estimates i would like to have happen a version history done where once a quote is created that it cannot be modified but rather a new one created with a "dash" number or letter to indicate the revision history..
Ie. original quote was 20465 created by "Shaun".. "Bob" wants to add a part to that quote but he wont be allowed to modify it but rather have to create 20465-1 - and so on.
I'd like to hear from anyone that has done this and if it affects the autonumbering schema in Netsuite.
0