Finding Reports That Reference a Specific Custom Field | Community
Skip to main content
Level 2
August 12, 2026
Question

Finding Reports That Reference a Specific Custom Field

  • August 12, 2026
  • 1 reply
  • 15 views

How do you identify reports impacted by a field change?

As I work to modernize our decade-old Workfront instance in preparation for Planning, Fusion, and future AI capabilities, I'm finding it increasingly difficult to identify which reports are impacted when a custom field is updated, consolidated, or retired.

We currently have more than 700 reports, and I haven't found an efficient way to identify which reports reference a specific field.

For example, we recently consolidated several legacy Yes/No fields into a single multi-select field. The new design is cleaner and easier to maintain, but now I need to identify all reports that:

  • Filter on any of the retired Yes/No fields

  • Display those fields as columns

  • Group by those fields

  • Use those fields in chart configurations

  • Include them in prompts or other reporting logic

Today, the only approach I know of is manually reviewing reports, which is not realistic at this scale.

 

Questions for the community:

  1. Is there a way to report on report definitions and identify reports that reference a particular custom field?

  2. Has anyone found a reliable API, text-mode, or Fusion-based solution for impact analysis when changing or retiring fields?

  3. How are other large Workfront instances managing report dependency tracking and technical debt?

As our environment grows, understanding the impact of a field change before making it feels increasingly important, and I'm curious whether others have developed a scalable approach.

1 reply

skyehansen
Adobe Champion and Community Advisor
August 13, 2026

Q1: ways to report on definitions:

 

Ideally before even starting, you would run a report usage report and ignore or delete any report that had not been viewed in over one year.

 

Other than this my other suggestions:

 

  1. the field report has a column for reports. You could start with this.

 

  1. there is also this sample report that will pull everything out of all reports as display it as text mode. It’s not great but you can download to excel and word search on each of the columns.  Once you learn the text mode you might wish to run the same text mode on your views, groupings and filters area in the setup to retire those views, groupings and filters.

https://experienceleague.adobe.com/en/docs/workfront/using/reporting/reports/custom-view-samples/view-reporting-elements-used-reports

 

The above two ways are very beginner friendly.

 

Q2: other ways to do impact analysis

Other beginner friendly ways might be to engage with a solution like https://store.atappstore.com/product/health-checker/ or as you said, develop something in house with Fusion. 

 

Q3: dependencies and tech debt

From a governance perspective, I always advocate for thoroughly documenting every implementation including the reports developed for that implementation, and commit to supporting those; AND naming/tagging your fields specifically for each implementation. With these two in mind, if you are impacting a Marketing field, and you have a list of Marketing reports that you are committed to supporting, then it becomes very academic to make the changeover. Similarly even if you do not have your fields tagged, you can see which forms they are being used in, and target those workflows’ reports.

(For these and other governance, maintenance and reporting ideas, see https://business.adobe.com/summit/2026/sessions/skill-exchange-5-key-areas-to-address-in-your-work-s908.html )