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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Please note that on Saturday, April 18, 2026, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 15 minutes. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
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