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.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover 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. Register now
Join the NetSuite community to innovate, connect, and discover 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. Register now
Coldfusion 8 POST request to a Suitelet - "405 Method Not Allowed"
We're having problems in completing POST between Coldfusion 8 server and the Netsuite sandbox (with script, deploy, compid & h variables in the URL). We're using the standard <CFHTTP> POST method on the server and Netsuite is returning a "405 Method Not Allowed" message.
When we POST all content (including script, deploy, compid & h) we get a "206 Partial Content" result.
However, when we GET all data - we get a "200 OK" response.
Support has asked us to add additional CGI variables to the post, which we've done, and this has changed the 405 into the 206 result for the POST.
An example of the request and result is here:
0