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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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!
SuiteWorld 2025 registration is officially OPEN
SuiteWorld is the largest annual gathering of the NetSuite community! It will be held in Las Vegas on October 6-9, 2025. Our customers and partners look forward to SuiteWorld every year as a place to hear the latest from NetSuite, get hands-on learning, and connect with each other. Register now!
SuiteWorld is the largest annual gathering of the NetSuite community! It will be held in Las Vegas on October 6-9, 2025. Our customers and partners look forward to SuiteWorld every year as a place to hear the latest from NetSuite, get hands-on learning, and connect with each other. Register now!
Starting June 1st, 2025, you may notice that our regular e-Fix releases are being referred to as ‘Minor Releases’. It’s still the same release schedule, with a different name. (Link can be found here)
Why throwing an error in Async entry point Function gives unexpected error?
Has anyone had an issue using the async
keyword in entry point functions such as post
or get
in RESTlet script types?
Our team has noticed that if you make a entry point function like post
async, it results in an unexpected error if you throw anything. For example, the simple script below, it is responding with an unexpected error:
/** *@NApiVersion 2.1 *@NScriptType Restlet */ define( ["N/error"], function (error) { async function _post(context) { throw error.create({ name: "MY_ERROR", message: "This is my error" }) } return { post: _post, }; });
JSON Response:
{ "error": { "code": "UNEXPECTED_ERROR", "message": "An unexpected SuiteScript error has occurred" } }
We would have expect it to respond with this though:
0