You need to sign in to do that
Don't have an account?
Marcelo Tudisco
outbound change set to production dependencies
Hi, i have just created a new developer sandbox, on that sandbox I create a before delete trigger on CampaignMember, i create a test class and do the tests to get code coverage. After that i create a new outbound change set with the trigger to upload it to production. If i just add the trigger to the change set (no dependencies), when i go to production and in the inboud change set try to validate it, it fails because i do not satisfy code coverage. If on the sandbox i add the trigger and add all dependencies then i can deploy it on production. In those dependencies it adds a custom field and a global value set.
Can anyone explain me why it adds that custom field and that global value set as dependant when they are already on production? Why does the validate on production fails if i dont add the dependencies to the change set, even though those depencies already exists on production?
thanks
Can anyone explain me why it adds that custom field and that global value set as dependant when they are already on production? Why does the validate on production fails if i dont add the dependencies to the change set, even though those depencies already exists on production?
thanks
Run Specified Tests
Only the tests that you specify are run. Provide the names of test classes in a comma-separated list.
View and Add Dependent Components to a Change Set
From Setup, enter Outbound Change Sets in the Quick Find box, then select Outbound Change Sets.
In the Change Sets list, click the name of a change set.
Click View/Add Dependencies.
On the Component Dependencies page, select the dependent components you wish to deploy and click Add to Change Set.