Related Support Case # 00282241
The support person in the above case suggested I post this idea here.

I need to delete around 85 fields from a database.

All the fields have dependencies which need removing before I can delete the field so I run the Field Usage Report to determine these.  The problem is the Field Usage Report does not list dependent import jobs which would be really useful as I can't delete the field without removing dependencies related to these as well.  Even if I delete the field and the job says it was successful it does not disappear from the database.

So I've got no easy way of knowing which import jobs reference a certain field that I want to delete.  I'm faced with the nightmare of having to somehow work this out for 85 fields.

Reply from support person.........
'I have investigated this matter more thoroughly and was able to find that for the database " dbEnergy-Environment " there are couple of recurring import jobs set up.
If you delete a field from your Acoustic Campaign database, but you still see the field, this is because the field is referenced in a recurring Import field mapping file that was created before the field was deleted. Even after the field is deleted, the field is recreated the next time the import job runs.'

See the support ticket for the whole picture on the issue.

So the request is to please add ALL dependencies to the Field Usage Report or it's a bit worthless.