Customs Fields reportable through a Typeahead Object

I see this thread is from a few years ago and I'm experiencing this issue as well. Has this been addressed? 

Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!

Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.

Did this ever get any follow-up? 

Typeaheads are functionally useless for most applications within Workfront that I come up with. It's been about a 1/2 year. Any news?

Hi - with today's change to "not planned" could you clarify the reason for it not being planned? Does Reporting 2.0's new framework make this no longer needed?

Today we have multiple Fusion jobs copying data from one object to another as a workaround. Those jobs & the resulting duplication of data are creating maintenance costs for both Workfront & us. Additionally, support is blaming the reporting hoops we're having to jump through on performance issues that are giving a negative impression of Workfront to Executive users of Workfront.

Hi - with today's change to "not planned" could you clarify the reason for it not being planned? Does Reporting 2.0's new framework make this no longer needed?

Today we have multiple Fusion jobs copying data from one object to another as a workaround. Those jobs & the resulting duplication of data are creating maintenance costs for both Workfront & us. Additionally, support is blaming the reporting hoops we're having to jump through on performance issues that are giving a negative impression of Workfront to Executive users of Workfront.

Typeahead fields are usless with out linking to the parent object... but you knew this.

Why are so many things in Workfront "halfway done"?

Typeahead fields are usless with out linking to the parent object... but you knew this.

Why are so many things in Workfront "halfway done"?

Having this de-prioritized is a major setback. Personally, I run into the need for this with a large percentage of the reports I run into. There is such rich data that can come from having a typeahead field populate additional data points for reporting, etc. It is very disappointing to hear that this was moved back in priorities. I hope this becomes prioritized again very soon.

Having this de-prioritized is a major setback. Personally, I run into the need for this with a large percentage of the reports I run into. There is such rich data that can come from having a typeahead field populate additional data points for reporting, etc. It is very disappointing to hear that this was moved back in priorities. I hope this becomes prioritized again very soon.

That's a really good use for project relationships, Cameron. I could definitely use that.

I want to use it for creating a required "Company" field in a project that pulls companies of type "Client" in and filtering out vendors. This way I could pull client info into a project, like product name & code, client name & code, region, client contact, billing schedule, etc.

Currently, I had to create a Fusion automation that looked at a custom (and required) field called "Client" and copy the choice to the built-in "Company" field. The name "Company" never made sense because it was a client or vendor we were choosing.