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
WSDL 2.5 Beta - Login problem
I have a .NET Web Services application that uses the 2.0.0 WSDL, and I want to start developing against the 2.5 Beta WSDL to take advantage of the new record types. (We won't use this app in production until the WSDL is released.) However, after updating to the new web reference, my client application is no longer able to log in to NetSuite. When I call the login method of the service object, I get this error:
The AXIS Engine could not find a target service to invoke! targetService is NetSuitePort_2_5
Here is the code that I use to log in to NetSuite (which works against WSDL 2.0, but not 2.5):
0