megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
Don't miss out on our Pop Quizzes! #1 | #2 | #3 | #4 | #5 You only have until tomorrow, March 20, 2026, 1:00PM ET to comment your answers.

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!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.

INSUFFICIENT_PERMISSION Error on SalesOrder add when setting custom form

edited Dec 2, 2019 3:03PM in SuiteCloud / Customization 1 comment

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="

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders