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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
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