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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week! You only have until tomorrow, September 11, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
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!
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!
Invalid shipmethod reference key (WSDL)
When trying to mark Drop Ship Purchase Orders as shipped via WSDL I'm receiving the following:
"ERROR: INVALID_KEY_OR_REF - Invalid shipmethod reference key 3"
A similar same issue was reported as an issue with the UI here:
https://usergroup.netsuite.com/users/showthread.php?p=103266
The process I am running was originally developed on WSDL v2.6. It ran without issue or change since v2.6. I updated it today to v2009.1 and received the same error.
I've tried forcing the shipstatus via:
oItemFulfillment.shipStatus = ItemFulfillmentShipStatus._shipped
Next I will try forcing the shipmethod based on what is defined on the PO.
0