RE: 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:

 * @NApiVersion 2.1
 * @NModuleScope Public

Why would the “SameAccount” scope be applied here?

jeremy Rookie Asked on November 3, 2020 in SuiteCloud.

Has this been resolved already?


on March 2, 2021.
Add Comment
1 Answers

As with all problems in SuiteScript 2.1 related scripts, do it in SuiteScript 2.0 first to see if its a 2.1 related problem.

Advanced Answered on November 3, 2020.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.