We have a bundle that was done by our implementati...
# sdf
c
We have a bundle that was done by our implementation partner as part of our go live migration from our sandbox environment. Not sure why they chose to lock a custom field on install. If I convert if into a SDF project, would it be possible to unlock it, and redeploy? Can this be done without being a sdn member?
j
I also find that their SuiteScript is 2.x and they're my only offenders. Now I have to look at a gross banner about 2.1 migration.
s
do you still own the bundle in sandbox? seems like that would be the more direct route to fix it, no?
c
Unfortunately that was two years ago, and several refreshes later. My assumption would be we don't. How can I verify?
s
the “several refreshes” already answered the question, alas
c
You'd think there would be a mechanism for bundles not linked to SuiteApp to be editable/owned by the account directly automatically.
m
Hi @Christopher Quackenbush, did you try the Dissolve action? docs.oracle.com/en/cloud/…/section_3770244609.html Once dissolved, I expect the record to no longer be locked, given that the lock setting comes from the bundle definition.
cc: @Milan Kostelnik
@Jamie Houselog, are you not able to update the scripts to 2.1 because the scripts are locked?