This topic contains 0 replies, has 0 voices, and was last updated by silverriaz 5 years, 10 months ago.
-
Posts
-
silverriaz- Contributions: 0
- Level 1
- ☆
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
However, since today, I get only 2.0 orgs pulled into library, even if my SuiteScript is in 1.0.
I was just wondering if this is an accepted behaviour and whether should I change one of my library files to prevent namespace clash.
Best,
Riaz G
This is a cached copy. Click here to see the original post.
You must be logged in to reply to this topic.