Hi everyone, I’m getting an error when trying to install a bundle that contains extensions:

Installation Script Error  
JS_EXCEPTION  

org.mozilla.javascript.EcmaError: TypeError: Cannot read property "parent" from null  
(/SuiteBundles/Bundle 521562/CommonUtilities/UtilsSS2.js#57)

I’m using the ExtensionBundleSS2.js installation script. However, since this is a Sandbox-to-Sandbox deployment, there’s no /SuiteBundles/ folder created. The Extension Manager SDK expects the extensions to be located inside that folder, which causes the script to fail with the error above. Is there any known workaround or recommended approach for this scenario?

That's the bundle that puts the dev tools in the file cabinet. There's really not anything to do with it except download the extension and theme dev tools.

I’m following this guide: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1527275163.html. I need to create a bundle with a couple of extensions and install it in another sandbox.

Oh, you've created an extension, then bundled it, and now you're trying to install it into another account from Customization => SuiteBundler => Search and Install Bundles ?

Exactly, and when I try to install my bundle, I get this error

Installation Script Error  
JS_EXCEPTION  

org.mozilla.javascript.EcmaError: TypeError: Cannot read property "parent" from null  
(/SuiteBundles/Bundle 521562/CommonUtilities/UtilsSS2.js#57)

Well, if you look in the file cabinet, at

UtilsSS2.js

and search for

parent

here's the function that's borking:

,   getBundleFolderPath: function getBundleFolderPath(folderId)
        {
            var bundleFolder = FileApi.getFolder(folderId, ['parent']);

            return '/' + bundleFolder.parent[0].text + '/' + bundleFolder.name;
        }

I think the issue is that, since this is a Sandbox-to-Sandbox installation, the files aren’t created in the SuiteBundles folders. The

getBundleFolderId

method in

UtilsSS2

does this:

var folderId = bundleId ? FileApi.searchFolder('Bundle ' + bundleId, '-16') : null;

What makes SB different?

The /SuiteBundles/Bundle [ID]/ path is only created for bundles installed from Production accounts.

I don't, and that blog post is over 5 years old so things could have changed since I wrote it