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.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
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.