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.
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

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders