Book Image

DevOps for Salesforce

By : Priyanka Dive, Nagraj Gornalli
Book Image

DevOps for Salesforce

By: Priyanka Dive, Nagraj Gornalli

Overview of this book

Salesforce is one of the top CRM tools used these days, and with its immense functionalities and features, it eases the functioning of an enterprise in various areas of sales, marketing, and finance, among others. Deploying Salesforce applications is a tricky event, and it can get quite taxing for admins and consultants. This book addresses all the problems that you might encounter while trying to deploy your applications and shows you how to resort to DevOps to take these challenges head on. Beginning with an overview of the development and delivery process of a Salesforce app, DevOps for Salesforce covers various types of sandboxing and helps you understand when to choose which type. You will then see how different it is to deploy with Salesforce as compared to deploying with another app. You will learn how to leverage a migration tool and automate deployment using the latest and most popular tools in the ecosystem. This book explores topics such as version control and DevOps techniques such as Continuous Integration, Continuous Delivery, and testing. Finally, the book will conclude by showing you how to track bugs in your application changes using monitoring tools and how to quantify your productivity and ROI. By the end of the book, you will have acquired skills to create, test, and effectively deploy your applications by leveraging the features of DevOps.
Table of Contents (14 chapters)
Title Page
Packt Upsell

Deleting files/components from a Salesforce organization using destructiveChanges.xml

We have seen we can retrieve metadata from a sandbox, and we can deploy changes to a sandbox using the Ant Migration Tool. But sometimes we don't need some features and we want to delete some components or files such as objects, fields, and so on from our Salesforce organization. We need to create one more file along with package.xml that is destructiveChanges.xml. The format of the destructiveChanges.xmldelete manifest will be the same as package.xml, only wildcard characters are not accepted in a delete manifest.

Delete component is same process as deploying components with delete manifest file. We need to add a list of the components to delete in destructiveChanges.xml. A sample file to delete a custom object is as follows:

<?xml version="1.0" encoding="UTF-8"?> 
    <Package xmlns="">