Have you ever tried to assess which reports would be impacted by changing or deleting a custom field? This idea addresses that: https://one.workfront.com/s/idea/0874X000000sYWZQA2/detail.
(Personally, I would never recommend deleting a field, however this may sometimes be necessary.)
Respond here if you'd be interested in providing early feedback on a concept. Thanks!
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @jeremy. I am not sure that finding fields for "deleting" is the issue. It's more about determining the impact a field change could have. We had to do this for a client. Use Case was about finding what reports were impacted by making the field "change" so that the report could be edited - (e.g. update a custom header).
One of my fellow consultants at Rego actually build something to help with this. Reach out to learn more.