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.
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!
SCA Mont Blanc, Release 2016.2, error in shopping-local.ssp
Hi, we are experiencing a problem when running SCA Mont Blanc locally (i.e. via gulp local). The problem appears to have been occurring since our account was recently upgraded to Release 2016.2.
Whenever the browser (Chrome) displays a page in the Shopping application (i.e. via shopping-local.ssp), the page displays, but the cursor has a persistent spinning circle (loading graphic), which does not disappear. I can verify this also occurs in a "vanilla" Mont Blanc development project with no customization.
Has anyone else experienced this? Is this a defect introduced in 2016.2? Is there a get-around?
[ATTACH=CONFIG]n415968[/ATTACH]
0