Skip to main content
Level 2
May 19, 2026
Question

View not showing values

  • May 19, 2026
  • 2 replies
  • 18 views

Hello,

 

I have a 2 custom forms, one at the project level, the other at the issue level. They both have 2 typehead fields that both live on each level. When trying to pull the value at the issue level I do not get a value. The view never gives me the option to pick between what level. Any help would be greatly appreciated. 

    2 replies

    KellieGardner
    Community Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 20, 2026

    Hi ​@BruceMe7  - Trying to understand what you are trying to do here.

     

    You said, “When trying to pull the value at the issue level, I do not get a value.” Are you trying to pull the value on the project onto a report or view for an issue? If so, this functionality is limited.

     

    There is a workaround, though deep in some other threads.

     

    “In the meantime, you can use a calculated field on the Project to display the value of the corresponding Typeahead field. Then that calculated field can be used in reporting just as usual. Example calculation would be: {Typeahead Field Name:name}”

     

    I haven’t tried any of these, just seen the posts. 

    Adobe Support
    May 25, 2026

    Hi ​@BruceMe7 ,I’m assuming this is mainly for reporting purposes, the workaround would be to explicitly reference the project-level field from the issue level rather than relying on the report/view to distinguish between similarly named fields automatically. Since Workfront treats project and issue custom fields as separate fields internally, even when they share the same label, the recommended approach is to create a calculated field on the issue custom form that pulls the project-level value using syntax like {project}.{DE}. For typeahead fields specifically, you may need to use {project}.{DE:FieldName} to return the display value correctly.

    Another option is to include separate report columns for the project-level and issue-level fields so each field is referenced independently rather than expecting the view to dynamically choose between object levels or use EXISTS filters and collections to bridge data between objects.