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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
odd XML errors on web services requests
Has anyone else encountered strange errors related to XML parsing on your web services requests recently? A few days ago we started seeing an unusual number of error responses like this:
org.xml.sax.SAXParseException: The element type "n5:escription" must be terminated by the matching end-tag "</n5:escription>"
org.xml.sax.SAXException: Invalid type: {urn:core_2008_2.platform.webservices.netsuite.com}BooleanCustomFielRef
org.xml.sax.SAXException: Invalid type: {urn:core_2008_2.platform.webservices.netsuite.com}StringCustomFieldef
I'm by no means a perfect typist, but I would swear on a stack of twenties that these misspellings appear nowhere in our application code. The odd part is that the error is the same for a given request (i.e. a given sales order) and so it is repeatable. I have produced wiredumps showing exactly what we're sending, and it looks fine here. However, the error makes it look like single characters are being dropped somewhere along the way. Am I going crazy here?