Avoid spurious differences in LeadConvert
SFDC seems to retrieve the lead convert settings in non-deterministic order between orgs . Display only true changes/adds/deletes rather than differences in ordering of the mappings as they make no difference to the runtime execution of Lead Conversion
Eric Kintzer shared this idea
Is this the same issue as the one documented at https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different or is there more/different nuance to LeadConvert?