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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Diagnosing Unexpected Errors
Simple question. When a web service (or I suppose anything else for that matter) returns an "Unexpected Error" and provides an Error ID, is there any way to get more information about what's wrong? My experience with web services has been very frustrating because anything but the most trivial mistakes are punished with these useless responses, and I end up spending most of my time on trial/error debugging.
I apologize if this question has been answered already, but as you might imagine, searching the forums for "unexpected error" produces an epic list of threads. Reviewing a few samples suggests that further detail exists, but that the only way to find out the nature of the failure is to file a ticket with support, which as a rather serious problem for a "self-service" customer. I would expect paid support customers to be annoyed as well, given my experience with the availability and responsiveness of support.