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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
INSUFFICIENT_PERMISSION Error on SalesOrder add when setting custom form
Any ideas as to why when we upgraded our SuiteTalk code from 2009_1 to 2011_1 we suddenly started getting INSUFFICIENT_PERMISSION errors when setting the custom form on a Sales Order record add? I commented out the line of code that set the custom form value, and that error went away. I also went back and tried our original 2009_1 code, and that worked fine. The only thing we changed was 2009_1 to 2011_1 in any references to full class paths, namespace references, etc.
Here's a sample SOAP request (with name, address, other private data altered) and response.
Request:
<?xml version="1.0"?> -<soapenv:Envelope xmlns:soapenv=" 0