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
Inconsistent behavior on search and getList with the 2.0 interface
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.