ZDoNotUse - (original name)
ZToBeDeleted - (original name)
ZNotinUse - (original name)
ZDepreciated - (original name)
The power of the Z's. Why Z? When you tag a field with the first letter Z and your sort alphabetically the field or entity or view or chart or dashboard appears at the bottom of the list.
When you browse field in Advanced find, the fields starting with Z appear at the bottom of the list and when you are looking to do a quick cleanup, having all fields you want to delete start with Z can make life just a little bit easier.
So why would you flag a field ZToBeDeleted - (original name)? Why not just delete the field?
Well, if you have not experienced this first hand, Microsoft Dynamics 365 Build and Release processes MERGE, so if you delete a field in your development environment and you don't delete that field in your test environment, then the field will still exist after your build and release.
It should be noted that there are MANY different types of builds and releases and managed solutions bring a different dimension into this conversation, so let's just assume unmanaged solutions and manual build and release (for the sake of this conversation)
If you train your team to name every field that needs to be depreciated ZToBeDeleted - (original name) and you define a process where you then delete these in batch in ALL environments, then you can save yourself numerous hours of detective work.
The other tidbit is to mark any fields that are labeled with a Zxxxx - (original name) with an unchecked SEARCHABLE AND the awesome team at Microsoft slipped in a little handy trick for doing this quickly. You can now select a set of fields and use BULK EDIT to change three things.
1) AUDIT Yes/No
2) SEARCHABLE Yes/No
3) REQUIRED Yes/No