Changing Locked Package dependencies after they are deployed

We found some validation errors indicating we have a package hierarchy issue on an older package that already deployed to production.  To resolve this, we need to unlock some packages and change their dependencies.  While I am able to unlock them with the following script below, I still can't change the package dependencies even when unlocked.  How can I change the package dependencies on a package that has already deployed?

DECLARE @packageName nvarchar(50); 
SET @packageName = 'Package_Name'; 
UPDATE SysPackage 
SET IsChanged = 0, 
    InstallType = 1, 
    IsLocked = 0, 
    Maintainer = 'Customer' 
WHERE Name = @packageName 
AND SysWorkspaceId IN (SELECT 
  Id 
FROM SysWorkspace 
WHERE Name = 'Default'); 
UPDATE SysSchema 
SET IsChanged = 0, 
    IsLocked = 0
FROM SysSchema 
JOIN SysPackage 
  ON SysSchema.SysPackageId = SysPackage.Id 
WHERE SysPackage.name = @packageName 		
Like 1

Like

3 comments

Hello,

Please note that we do not recommend making changes to this package on the end environment. It is best for you to fix the issue with the dependencies on the dev site and then transfer the package with the updated dependencies to prod again. It will ensure that in future, if you decide to transfer this package or a connected package to prod again, it does not override your settings and the system's integrity is preserved.

Mira Dmitruk,

Hi Mira, thank you.  I understand that and am trying to make changes in our development environment.  That is where I am encountering this issue where I cannot change the package dependencies even when they are unlocked.

Francine Braese,

Please describe which errors exactly you get when trying to change the dependencies.

Show all comments