Level 2

Declined

Customs Fields reportable through a Typeahead Object

Forum|Forum|6 years ago
September 23, 2019
18 risposte
2675 visualizzazioni

We should be able to reference custom fields associated to a Typeahead object through Calculated Custom Fields and Calculated Columns.

valuefield=[Typeahead Field Name]:[Custom Field]

Ex. My organization uses a User Custom Form to track employee details such as 'Department' or 'Employee Number'. When a request is submitted on behalf of another employee we would like to use the Typeahead field to identify the employee and then have a set of calculated custom fields to 'auto fill' in the rest of the employee details.

Mostra risposte precedenti

C

Cameron_Ward

Level 3

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.

RandyRoberts

Community Advisor

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

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

RandyRoberts

Community Advisor

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

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

Jason_JB

Level 5

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.

Jason_JB

Level 5

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.

JMitchell44

Level 2

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?

Vazgen_Babayan

Adobe Employee

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.

S

SanchoMa

Level 2

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

Registrati

Accesso al social

Accedi alla community

Accesso al social

Scansione del file per virus.

Questo file non può essere scaricato