[mpn]

I had been coding in sandbox then updating a bundle in prod to get these updated files.

All simple and good – then the customer did a sandbox refresh.

Now, SOME of the files are there in sandbox, but they’re in a “SuiteScripts/SuiteBundle” path, and still SOME are there but not editable (i.e. if you go to the file record, there’s no “Edit” link). I thought I would make a new bundle (a bit ugly since the files have that bundle path, but oh well), but some of the files are just plain inaccessible now.

Has anyone dealt with this? Is there any way to recover?
This is a cached copy. Click here to see the original post.

[mpn]

… and I guess there’s also the question of if this whole approach is wrong, although I’m more keen to just be able to pull files from sandbox again.

[smehta]

mpn,

If I understand your question correctly, these uneditable files are the ones that you developed in Sandbox prior to refresh?

[mpn]

smehta,

Sorry, yes, that is right. These were developed on sandbox, deployed to prod via a bundle, and then the refresh occurred.

[smehta]

In the bundle definition, were these marked as “Lock on install”. Locking will make it un-editable in the account where its installed and I believe this is true for bundles coming from sandbox too.

Please check if those files which are uneditable if they were “locked’ in the bundle prior to install on production.

[Author]

Posts