Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Reporting on Typeahead Fields

Avatar

Level 9
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
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

26 Replies

Avatar

Level 7
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

Avatar

Level 10
yep -- agree with Terry. Anthony are you not finding the field under Project > Custom field name? -skye

Avatar

Level 10
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

Avatar

Level 9
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

Avatar

Level 10
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

Avatar

Level 10
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

Avatar

Level 9
I appreciate the suggestion Doug, but no dice. No data appeared in the field. Anthony Pernice Healthcare Consultancy Group

Avatar

Level 7
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

Avatar

Level 10
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

Avatar

Level 3
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

Avatar

Level 9
And we have a winner! Thanks everyone! Anthony Pernice Healthcare Consultancy Group

Avatar

Level 2
Hey @Josh Hardman , I'm having a hard time getting this to work for me. I have a typeahead user field on a task form. On the same form I have a calculated field to show if the user in the typeahead field is active. User Typeahead field name: Hardware Assigned To Calculated field name: Hardware User Status Calculated field format: text Calculation: {Hardware Assigned To:Is Active} On a task an active user is selected in the typeahead field, but the calculated field is still blank. I've recalcuated custom data, removed the user and put them back in the typeahead, opened and saved the custom form, still nothing is calculating. Any advice? Cory **UPDATE 7/23/19 I found that using camel case on the field name works for system fields. This is pulling a system field from the user in the typeahead field and displaying it in the calculated field on the same form: {Hardware Assigned To:isActive} I have not figured out how to pull in custom fields from the user in the typeahead field yet. Cory Anderson Cisco Systems- Communication Services

Avatar

Level 3
I believe you have to use the actual field name, not the label. So try this: {Hardware Assigned To:isActive} Josh Hardman Product Manager, Workfront

Avatar

Level 2
Thanks Josh! I did figure that part out, but cannot figure out how to get data from custom fields that are attached to the user named in the typeahead field. Is that possible? Thanks, Cory Cory Anderson Cisco Systems- Communication Services

Avatar

Level 3
Unfortunately you can only access user native fields. Josh Hardman Product Manager, Workfront

Avatar

Level 5
I have a field called Backup Requestor on my Request. I am trying to put a calculated field on my Project to get the name to pull through, so I can use it on other reports, but cannot figure out what to put in the calculation to get it to work. Any suggestions for what to put in the Calculation box? Kristine Ross Empower-Retirement

Avatar

Level 7
Hey Kristine, Per Josh's note above: 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. So for your scenario, the calculation should be: {Backup Requestor:name} Thanks! Dustin Martin Assigned Support Engineer Workfront

Avatar

Level 5
I get the Custom Expression Invalid Kristine Ross Empower-Retirement

Avatar

Level 10
Kristine: You can't pull information from an existing request's custom form into a project custom form as far as I know. You can do a one-time copy--when you convert a request to a project it will pull the request information over at that point, but that's about it. -skye

Avatar

Level 7
Aha Skye caught my mistake.. I didn't pay enough attention. The issue you'll run into Kristine is that the project object is 'above' the issue object. So you can do a collections, but that can only be done on a view, not as a calculated field. The reason behind this is because you can have multiple issues on a project, so the system has no idea which issue you're referring to. Hope that helps! Thanks, Dustin Martin Assigned Support Engineer Workfront