#Force.com ant migration tool how to
#Force.com ant migration tool update
#Force.com ant migration tool code

#Force.com ant migration tool code

The reason I use VS Code is that it can do syntax formatting and tell me if thereвЂ™s bad XML before I even try and upload it. What I like to do is use VSCode to create the two required XML files which are called вЂњpackage.xmlвЂќ and вЂњdestructiveChanges.xmlвЂќ. DonвЂ™t worry, creating the files is pretty easy and should only take a few minutes for a dozen or so deletes. You will need to click the вЂњAllowвЂќ button so that you can access.Д«efore we upload the files to workbench to do the deletions we need to create the files. When logging in itвЂ™s important to make sure that you use the correct Environment (Production for Developer Orgs and obviously Production orgs). My favourite thing about Workbench though is that I can do deletes easily through it without having to mess around with the Migration tool. It can do things like data inserts, updates, deletes, exports, and a lot more. Workbench is a web-based set of tools that are designed to allow administrators and developers to easily interact with Salesforce orgs. The file structure and files are identical because it is basically running the same process.

#Force.com ant migration tool how to

It doesnвЂ™t require learning the terminal or learning how to use the ANT. If you are infrequently doing deletions or deployments through the migration tool, Workbench is a better solution. The metadata should look something like this: Save to the server (you can do multiple together as long as the deletion order doesnвЂ™t matter and do one big save.).In the class or trigger, you want to delete, open the metadata file and change the status of the class to вЂњdeletedвЂќ.Use an IDE to create a new project and download all classes from production.Eclipse should figure out the differences between the two folders. Once you have made all of the necessary deletions deploy the entire class folder or trigger folder to production. The easiest way should be to perform any deletions that you need to accomplishin the IDE. Sfdx force:source:deploy -m ApexClass:SomeClass,ApexClass:SomeOtherClass,ApexTrigger:SomeAwesomeTrigger -l RunLocalTests -u AliasOfTheProject IDE Run the sfdx force deploy command with all of the classes/triggers separated by вЂњ,вЂќ using the terminal.

#Force.com ant migration tool update

Find the class or apex trigger we need to remove and update the metadata status to be вЂњDeletedвЂќ.

To do the delete we need to do the following steps: ThereвЂ™s a few different ways to delete the classes and triggers from Salesforce:Дoing deletions in VS Code is pretty easy and is my preferred way. I recommend at least commenting it out and then performing the deletion. In production, Apex classes and triggers cannot be deleted declaratively so thereвЂ™s a pretty inconvenient process that has to happen to remove them.Д«efore we can deploy any deletions when need to make sure we deploy updates to any version of code that remove the dependency.

As you might be aware, itвЂ™s not possible to modify Apex code directly in production so doing deletes can be really difficult.