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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
Custom SO body field for Cybersource payments
I'm looking at setting up a custom field to record the amount authorization by Cybersource on a Sales Order. Any ideas how I can script this?
I was looking at the sequence of beforeLoad/beforeSave/afterSave calls when saving a SalesOrder, and it looks like payment is processed through cybersource after the record is saved and before the record is loaded (view mode) again.
So if I'm not mistaken, if I want to calculate this authorized amount I would have to do this on a beforeLoad on a view.. I'm not sure if this is a good idea, since this would introduce the mutation in the view mode.. I would like to avoid those pesky "The record has changed" messages...
0