There are several Knowledgebase articles to assist with deleting duplicate and/or unwanted Addressees/Salutations. The one(s) to delete cannot be deleted while they are being used in records. However, once the user queries records that are using it (and also queries relationship records and a million other possible uses), then uses the query(ies) to globally change the choice to another option, commonly it still cannot be deleted because the pop-up error states that it is still in use in records. A couple ideas:

1. It would be helpful if the system would provide the list of areas where the item is still in use! That is what's hanging up deleting it afterall - and the user has to dig and deep-think through an endless maze of searching for where it could possibly be - and in my case - STILL come up dry! Users don't have the time!

2. Another thought is, why can't the clean up process that includes querying the addressee/salutation that one wants to delete from these various fields all be part of the steps, advise to use the queries to remove the selection from those records and globally replace it, and after going through several of these options, finally giving the user the option to delete the addressee/salutation 'at their own risk'?

   1. Once it's deleted, if there are these very hidden areas where the deleted addressee/salutation was being used, it wouldn't be hard to fix once it is discovered.

   2. Or there could be sidebar instructions showing how to query any addressee/salutations that are now blank and use global add to insert an available option.