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

Inconsistent behavior on search and getList with the 2.0 interface

edited May 28, 2020 9:05PM in SuiteCloud / Customization 3 comments

Hi there,

I've been experiencing inconsistent behavior with search and getList when using the 2.0 WSDL. We do not use the programming APIs to generate the SOAP messages, we're using XSLT. A message sent from our appliance to NetSuite for getList returns only a percentage of the listed records (even though they're valid ids), but the same message posted through SOAPScope works correctly.

Similarly, I was performing a search yesterday afternoon which consistently failed in both situations, but then started working again this morning even though the messages have not changed.

The message from SOAPScope is slightly different regarding namespace declarations, but the messages are semantically identical (they both validate against messages.xsd). I'm completely at a loss, but all indicators point towards the 2.0 interface being very touchy to the format of the message versus its semantic correctness.

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