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

Customs Fields reportable through a Typeahead Object

Avatar

Level 4

23-09-2019

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.

15 Comments

Avatar

Level 2

14-02-2022

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.

Avatar

Level 10

14-02-2022

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

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

Avatar

Level 10

14-02-2022

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

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

Avatar

Level 4

14-02-2022

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.

Avatar

Level 4

14-02-2022

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.