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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
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.