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?

Beginner Asked on March 2, 2021 in SuiteScript.
Add Comment
2 Answer(s)

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

Advanced Answered on March 2, 2021.
Add Comment

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

Rookie Answered on November 18, 2022.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.
  • This site made possible by our sponsors:   Tipalti   Celigo   Limebox   Become a Sponsor   Become a Sponsor