I am preparing a change set to deploy an updated trigger from sandbox to production. Now, there are associated classes and other dependencies. Do I have to add all the dependencies in the 'Add dependencies' section along with it ? This is my first time using a change set.
Add a comment
|
1 Answer
No, a changeset isn't any different from any other deployment method in this regard.
If you have code that uses a particular custom field, that field will (or should) show up as a dependency. If that field is already in your target org, then there's no need to deploy it again.
It boils down to "if there is a change between pieces of metadata in 2 orgs, deploy the things that changed".
-
Thank you and does it also mean that I would not have to add helper classes as well since I have not added anything new in those classes. Am I correct ? Commented Jul 6, 2020 at 13:05
-
1@user3920709 If it exists in your target org, and there are no differences in the metadata in the two orgs, then it doesn't need to be deployed. The feature name should give you a clue here. A Change set is something you use to deploy changes.– Derek FCommented Jul 6, 2020 at 13:09
-