Why would a module scoped as “Public” be evaluated as “SameAccount”?
An error like below occurs when a module is loaded via RESTlet in an installed account:
NO_PERMISSION_TO_MODULESCOPE_SAMEACCOUNT_MODULE : You do not have permission to load this module SuiteBundles/Bundle XXXXX/…, it has an @NModuleScope of SameAccount which restricts its availability to customization objects created in account(s) TSTDRVXXXXXX
The annotation on the module looks like this:
Why would the “SameAccount” scope be applied here?
Usual answer to weird things happening with 2.1 suitescript is to use 2.0 suitescript instead
hi, i know i am late but i was having the same problem and i solved it by adding the @NModuleScope Public module to my scripts. for further kindly see https://suiteanswers.custhelp.com/app/answers/detail/a_id/49326 and also this https://stackoverflow.com/questions/38058851/including-custom-modules-in-suitescript-2-0
