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.
Don't miss out on our Pop Quiz You only have until November 7, 2025, 2:00PM ET to comment your answers and earn rewards! Click here for more details.
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!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Accessing a Soap 1.2 Webservice
I am running Axis2 on my web server and in NetSuite, I wrote my client-side SuiteScript to use the Soap 1.2 namespaces.
Axis2 is saying that my transport level information does not match Soap 1.2. I narrowed it down to the Content-Type header. When I look at the request I get from Netsuite, the content type is set to "text/xml". I know that Netsuite proxies my client-side HTTP calls made by nlapiRequestURL() so it looks like NetSuite is adding the content-type header. I tried setting it to "application/soap+xml" (like Soap 1.2 defines) in my client-side script but I still received "text/xml" on my server. It looks like NetSuite is
0