Destructive Package XML

Owned by George Thomas (Unlicensed)
Last updated: May 26, 2022 by Rajeswar Rajendran
3 min read

Opsera supports deletion of components over Salesforce pipeline execution in two ways:

  1. Based on the components that are deleted or renamed in Git Branch

  2. Using CSV Upload

 

Based on the components that are deleted or renamed in Git Branch

In the case of components that gets deleted/renamed from the Git branch, Users can pick and chose those deleted/renamed components on the Salesforce Pipeline Wizard and proceed with deleting the same against the targeted Salesforce Org.

Below is a scenario that describes the case where the files that are deleted and renamed (to a different name) are being deleted from the Org using the destructive manifest file.

  1. Delete 2 files and rename 2 files in a github branch

2. Configure the github Branch on SFDC Pipeline

3. Load components whose files are renamed/deleted & Load their date range

4. View the Files deleted/renamed on the list in Git files

5. In XML Viewer, The Files newly renamed are added on Package xml and the files deleted/renamed are listed under Destructive Package xml

6. Run the pipeline and view the deploy logs

Deployment Logs:

 

 

Using CSV Upload

Users can now proceed with deleting components by creating Destructive manifest file with the help of uploading a csv file having the component to be removed.

  1. Create a csv file. Provide the component details and provide the commit action as Removed for the file that needs to be removed.

     

  2. Open the Salesforce Pipeline wizard. Click on File/XML Upload File/XML Upload Process Tab. Upload the created CSV file.

     

  3. Click on Process File button. This will display the CSV file details. Click on Proceed with Selected File button to proceed further to next screen



     

  4. Click on Proceed button to view the components to be removed under the Destructive XML. Click on Next to proceed with executing the pipeline.




  5. After the Pipeline execution is complete, click on the record having Action as Report under the Pipeline Activity Logs section to view the details Summary.






 

Â