Reporting on Typeahead Fields | Community
Skip to main content
June 19, 2019
Question

Reporting on Typeahead Fields

  • June 19, 2019
  • 23 replies
  • 5430 views
Text mode has long been my achilles heel in Workfront, so I hope someone here can help me out. I have a Task report and I need to display information from a Project-level custom form, specifically one of the brand-new Typeahead fields. I can get the info to display easily in a Project report, but it doesn't show as an option in my Task report. Anyone know how I can use text mode to make this work? Thanks. Anthony Pernice Healthcare Consultancy Group
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

23 replies

June 19, 2019
Hi Anthony, the new Typeahead Field in a report is its own top level object. So, if you named the Typeahead field "ABC", in a Task Report, you should find this field in the column list as "ABC". See this Support video at the 3:20 mark - they show an example of creating an Issue Report and adding a Typeahead Field as a column to the report. I am assuming adding a Typeahead field to a Task Report would be similar. "https://vimeo.com/339168186/b3ba78f3f1">Reference Custom Data Typeahead Terry Hynd EBSCO Information Services
June 19, 2019
yep -- agree with Terry. Anthony are you not finding the field under Project > Custom field name? -skye
June 19, 2019
nevermind, it looks like that's the case (project typeahead field does not show up as an option in a task report). Anthony: can you just swap out in textmode for any other project custom field and let us know if that works? e.g. here's what I get: valuefield=project:test custom field linkedname=project valueformat=customDataLabelsAsString displayname= namekey=view.relatedcolumn textmode=true namekeyargkey.0=project namekeyargkey.1=test custom field querysort=DE:project:test custom field -skye
June 19, 2019
Thanks Skye, I think we're close... Its probably something I'm doing wrong, but instead of displaying the name, I get {"objCode":"USER","name":"Anthony Pernice","ID":"573a313f006eabd9d62efdfb8102d490"} I copied your code and replaced your "test custom field" with the name of my field: displayname= linkedname=project namekey=view.relatedcolumn namekeyargkey.0=project namekeyargkey.1=Embedded Art Director querysort=DE:project:Embedded Art Director textmode=true valuefield=project:Embedded Art Director valueformat=customDataLabelsAsString Anthony Pernice Healthcare Consultancy Group
June 19, 2019
well... that's close. I've been experimenting in Preview Sandbox since I figure I could use the practice. * I've managed to find out that the "DE:" part of the string is unnecessary (works either way, whether you have it on or not). * I've tried specifying name (project:Embedded Art Director:name) and that doesn't work. * I've tried a few other valueformats (I saw customReferenceObjectAsString was used in the project report, so I tried that, for example, as well as HTML--nothing working so far, other than the customdatalabelsasstring format) Maybe @Dustin Martin has a few other suggestions up his sleeve -skye
Doug_Den_Hoed__AtAppStore
Community Advisor
Community Advisor
June 19, 2019
Hi Anthony and Skye, Tracking (very interesting), and -- untested -- wonder if the NameKey directives are tripping things up, so suggest you try the following, using the "less is more" axiom, and my when-in-doubt-try-use-HTML valueformat rule of thumb: textmode=true displayname=Project Level Embedded Art Director valuefield=project:Embedded Art Director valueformat=HTML Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads
June 19, 2019
I appreciate the suggestion Doug, but no dice. No data appeared in the field. Anthony Pernice Healthcare Consultancy Group
June 19, 2019
Hey all, So... we're still building it on the back end, but the work-around for the time being would be to create a calculated field on the project, to reference the type-ahead field. (Courtesy of Josh Hardman!) From there, you can call the calculated field from the task level. =) Dustin Martin Assigned Support Engineer Workfront
VicSellers
Community Advisor
Community Advisor
July 26, 2023

Does anyone know if this was ever built out on the backend? I know this topic was from 2019 but still having issues referencing a typeahead field that is on the project level on a task report. Any insight would be greatly appreciated!

Doug_Den_Hoed__AtAppStore
Community Advisor
Community Advisor
July 26, 2023

 

Hi @vicsellers,

 

Although there is continued interest in being able to retrieve custom data from a typeahead field, at this time my understanding is that it is still only native fields (such as those mentioned on this thread above and below) that are supported, even with textmode.

 

Regards,

Doug

June 19, 2019
Thanks Dustin. I think I'm just going to hang tight and wait for the back end to catch up to the front end. No offense, I have a bunch of custom fields already and no inclination to add one more. I appreciate the answer though! Saves me from trying a bunch of other combinations. -skye
joshh79242137
June 19, 2019
Thanks for bringing this to my attention Dustin. Yes, we still have some things we could improve on for reporting here. But, as Dustin says, 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. The calculation would be: {Typeahead Field Name:name} FYI, you can replace "name" in the calculation with any direct user field to get that value such as "title", "emailAddr", etc. Josh Hardman Product Manager, Workfront
Adobe Employee
April 4, 2023

Hi,
Is there a way we can fetch custom fields instead of any direct fields?