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!
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
SuiteBundler file location - are descriptive urls really the answer?
Apologies if this is just my lack of understanding - I've been round in circles in the documentation so many times now.
I have a client side script that I am adding to a Suitelet through form.clientScriptModulePath and pointing to the file in the SuiteScripts folder. This works fine until I bundle the project and install it in another account and the path to the script changes.
I have resolved this issue by pointing to the SuiteBundles/bundle id folder. Obviously I need to know the bundle id for this to work though. I can see this causing issues in the future.
0