Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
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.