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!
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!
Sandbox - webservice url
We recently refreshed our sandbox and during the refresh the sandbox now sits with production using the _SB1 notation with the ability to choose to use Sandbox via the roles.
I just tried connecting to sandbox via webservice. I updated the account information. I am using the NetSuite Service locator endpoint which should return back the proper url endpoint to use. I am getting an endpoint returned but host doesn't exist.
<account>.suitetalk.api.sandbox.netsuite.com
This was an issue in the past when they first started the sandbox cutovers/rollouts and was resolved but since we we finally cutover the issue has popped back up. It looks like someone got a bit too eager deploying code that isn't fully setup yet.
0