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:
Why would the “SameAccount” scope be applied here?