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 Pop Quiz You only have until November 7, 2025, 2:00PM 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
Confirmed failure to deliver email responses / question regarding best practice
We have an open case that appeared shortly after upgrade and the problem has been confirmed. NetSuite email replies with attachments are not forwarded from NetSuite to our mail system after the upgrade. Previously we believed we could depend on receipt of email from customers and vendors.
The impact is that any email we send from NetSuite with an attachment or any attachment a customer adds to an email with a Netsuite address does not come to us in Outlook and as such, we have no way of knowing that a customer or vendor has emailed us.
At the request of support, we created an employee record using a gmail account to rule out our mail servers and Support then acknowledged that the problem was not in our system but in NetSuite.
0