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!
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.
Share Your SuiteWorld Experience & Earn a Special Badge!
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
SuiteScript 1.0 and 2.0 : Namespace clash between 1.0 and 2.0 AMD libraries
Hello,
Just curious if anyone started to note this behavior from today.
I have a suitescript library in 1.0 called "orgs". I have all my global utility files and constants that can be called by orgs.parameter in any SS 1.0 file provided I include orgs.js in the list of library files. Been working great for 1.0 scripts.
Since 2.0 came out, I created orgs.js in 2.0 too with equivalent functions. I call this file in my 2.0 scripts using AMD.define(), and works great too for 2.0 scripts.
Until today, both of these files coexisted independently and NetSuite called the appropriate library file based on the SuiteScript version. 1.0 or 2.0
Tagged:
0