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.
Updating bundle - what does Replace Existing Object actually mean?
I am updating a bundle from sandbox to production. One of the items is a saved search which has two columns on the results referring to custom fields.
In the bundle, it automatically includes these two custom fields, which is fine, even though they exist on production already. The problem is when I perform the update NetSuite sees the conflict with existing objects and my only options are Add and Rename OR Replace Existing Object
What does Replace Existing Object mean? These objects obviously have data associated with them in records. When it performs the replace, will the data be preserved or will it all get wiped out? This is critical and very confusing. Imagine saying "Oh go ahead and replace it since I haven't made any changes" and then it wipes out the previous object AND data and installs this new one.