Reporting on Typeahead Fields

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

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

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

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

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

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

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

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

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

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