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
The case of the (partially) vanishing shipaddress - line item shipping
Have been tracking down a nasty bug for quite a while with no luck. Heres what I know.
We are creating sales order records via suitescript and setting shipaddress (msr - shipaddress on line item) with an internal id of an addressbook record like this:
record.setCurrentLineItemValue('item', 'shipaddress', [addrbookaddrid] );
record.commitLineItem('item');
This almost always seems to work fine. However we find that when we have user event scripts (or client scripts) that read the value of the ship address
on these lines after the record has been saved, and there is no value. This ship to address mysteriously disappears. This happens seemingly randomly. We cannot reproduce the error, only catch it after the fact.
0