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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
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.
How can I default the FedEx ShipAlert recipients?
It seems that NetSuite recently updated to automatically populate the FedEx ShipAlert field with the same users listed in the "To Be Emailed" field on a Sales Order, or at least the field started populating recently within our instance. The problem we are running into is that our "To Be Emailed" list is often longer than the 41 characters supported by the FedEx ShipAlert recipient text box. This leads to "Unexpected errors" when trying to save an item fulfillment record.
I cannot find this field in the workflow UI. My first thought was to clear the FedEx ShipAlert field with a workflow, as we do not use this field with how we are setup today. It would be nice to be able to address this field via a script or workflow, but it doesn't seem to appear in the workflow UI and it's difficult to modify with scripts since it is not a stored value (that I am aware of). We want it to be blank for now, but as time goes on we might want to source the field