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?

madge Beginner Asked on March 2, 2021 in SuiteScript.
Add Comment
1 Answers

Usual answer to weird things happening with 2.1 suitescript is to use 2.0 suitescript instead

Intermediate Answered on March 2, 2021.
Add Comment

Your Answer

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