Add Pre and Post Destructive Changes to a Branch

Use destructive changes to remove Salesforce metadata components during deployment. You can configure them as Pre or Post to control when the deletions happen.

What Are Destructive Changes?

Destructive changes allow you to delete metadata from a Salesforce org as part of a deployment. For example, you may want to remove unused fields, classes, or components that are no longer required. In Revvy, destructive changes can be applied:

• Pre-destructive changes – deletions occur before the main deployment.

• Post-destructive changes – deletions occur after the main deployment.

Adding Destructive Changes

1. In the Components tab of a branch, scroll down to the Destructive Changes section.

2. Click Add Pre Destructive Changes or Add Post Destructive Changes.

3. Select the source:

   • Connection – choose a Salesforce org to pull metadata from.

   • Branch – choose an existing branch.

4. Select the components you want to delete.

5. Click Add to include them in the destructive changes list.

Managing Destructive Changes

• Once added, components appear in the Destructive Changes section with their deployment type (Pre or Post).

• Use the three dots menu to:

  • Edit – change the deployment type (switch between Pre and Post).

  • Delete – remove the destructive change entry.

Deployment

When you run a Deploy or Validate action, destructive changes are included automatically. They execute in sequence depending on whether they are Pre or Post.

Best Practices

• Use Pre destructive changes to remove metadata that might conflict with the new deployment.

• Use Post destructive changes for cleanup after the new components are deployed.

• Always validate deployments with destructive changes to ensure no critical metadata is deleted by mistake.