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.
Don't miss out on our Pop Quiz You only have until October 31, 2025, 2:00PM 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!
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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Sandbox Change and CDN
I hadn't done any major testing on my sandbox since the transition to system.netsuite.com until today and it appears relative paths to script files are broken.
Little more background I have some custom Suitelets who's layouts are controlled by a template file. In the template I have html markup and references to javascript files in the file cabinet. The urls of the javascript file are relative /core/media....
Perhaps this method of having a view represented in a template file with javascript src references to files in the file cabinet is un-conventional but I don't understand why NetSuite had to change the c and h parameter of file references on the sandbox after this NA sandbox transition.
0