megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
Don't miss out on our Question of the Week! You only have until tomorrow, March 19, 2026, 2:00PM ET to comment your answers.

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!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.

odd XML errors on web services requests

edited Dec 2, 2019 3:05PM in SuiteCloud / Customization 5 comments

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?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders