Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
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.