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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Creating a new record from a 3rd party online form
This is what I am trying to do. We use FormAssembly to collect data in an online form that we host on our website. FormAssembly has an HTTP Connector that I would like to use to post the data directly into a custom record I have created. Looking at the documentation on both ends it seems like it should be possible by creating a NetSuite Custom Online Form and then Posting the data from the Form Assembly form.
If I try this using the NetSuite External form URL I get the error below:
Please review the error(s) below.
•An error occured while submitting the data to a third-party service. The error returned is: 405 Method Not Allowed Error 405--Method Not Allowed From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.6 405 Method Not Allowed The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.