Built-In Custom Field Impact on Reports View

Forum|Forum|5 years ago
November 3, 2020
8 replies
1613 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

jerfloAuthor

Employee

Thank you to everyone who commented here and to those who provided feedback!

C

Chris_Thygersen

New Participant

Jeremy, Count me in for feedback!

C

ColleenGr3

New Participant

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.