Good day Everyone. My question is a follow up question for my first problem which is already answered here. This is the link of my first question Use Object from another manage Package without making my own package dependent to it. As what our mates here suggested my first problem can be solve using dynamic SObject and dynamic SOQL. My question is that, If I did some code that will make my managed package dependent to "Package B", can I remove the dependency by removing the part of the code that makes it dependent ? or once it is dependent it will always be dependent even if I remove some part of the code ? Thank you.
2 Answers
if you release a package which is dependent on package B then you cannot remove that dependency easily. You have to connect to salesforce to remove that dependency.
-
Thanks Mate. Is there any way to check if there are dependency created in my code before doing a manage package ?– HopeCommented Nov 2, 2017 at 6:29
-
1@Hope In the package screen that lists all the components the rightmost column will tell you if the item is from another package– EricCommented Nov 2, 2017 at 7:24
It may be possible if you roll back the version that caused the dependency to a beta package. This is only allowed if no subscribers have that version or later installed. You'll also need to create a case with support. Simply removing the component that caused the dependency to be created will not remove the dependency. This is why it is incredibly important that you take care not to create these dependencies in the first place.
-
Thank you for this. I have further question. Is there any way, that I can check if there are dependency created in my code before doing the package ?– HopeCommented Nov 2, 2017 at 6:27
-
2@Hope The "View Dependencies" button on your package should identify all dependencies detected. You should review this list before each upload.– sfdcfox ♦Commented Nov 2, 2017 at 7:02