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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, November 6, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Error occurred while sending the transaction email????
Is anyone else having this issue?
After entering a sales order in the Customer Center with either the "Standard Online Order - Invoice" or a customized "Online Order - Invoice" when you hit the "Submit & Email" I get the following error:
The transaction was entered successfully, but the following error occurred while sending the transaction email: An unexpected error occurred while sending the transaction email
This started happening after the latest update, as I have have been using this feature for a few years now.
I also went to the customer recored and select the "Send Transactions Via" to "Yes" which I guess means to always email the transactions via email which also caused the same error.
0