(if using VS Code, you will find this file downloaded to force-app\main\default\LeadConvertSettings\ in your project folder)įor example, you would delete these 4 lines contained within the Contact section to remove the Lead to Contact mapping for “Custom Lead Field 1”:
To unmap a Lead field mapping (aka, “delete” the lead field mapping) from your org, follow the instructions above to download the LeadConvertSettings metadata XML file to your org, simply delete the lines of code containing the mappings you wish to remove, then push the changes back to your org! Posting here to answer my own question – the answer was so obvious, it had eluded me for a while: prerequisite to mass delete the fields)? I’ve searched all over the web and no one seems to be able to figure this out. Thanks for helpful quick article, but how do you remove/unmap LeadConvertSettings mappings (change them back to “None”, e.g. (sorry, re-posting as XML snippets got treated as code in OP) But each LeadConvertSettings mapping has a more complicated hierarchical structure similar to below, so it would seem you’d need to specify all of these things:Ĭould you please explain and provide some examples with both standard and custom Lead fields of how you could use package.xml and/or destructivechanges.xml (whichever are the correct ones) to set a mapped Lead field back to “None”?
The mystery is that package.xml components seem to only use, , and tags. But is it actually just a regular package.xml deployment, because technically you can’t “delete” standard object fields or settings themselves you’re just changing the values?
Many people (including myself) were under the impression you have to use destructivechanges.xml plus a default package.xml file (with no components listed) to perform a destructive change. prequisitite to mass delete the fields)? I’ve searched all over the web and no one seems to be able to figure this out.