Customs Fields reportable through a Typeahead Object

[#1]

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.

[#2]

We use the "Primary Contact" field for this exact use-case. It defaults to the requestor's name but if they are submitting on someone else's behalf they can set the primary contact to the appropriate user

[#3]

We would love to be able to reference controlled lists via the typeahead field.

It would really enhance our custom form / request intake process it would also allow us to have master "lists" for things that we could then reference across all use cases to enhance consistency and naming conventions etc.

Maybe having under "system" or "interface" a typeahead lists - then users could create individual typeahead lists that the system could reference similar to portfolios or users

[#4]

Hi Erich - I have been in talks with Product and allowing all object fields for type ahead fields is something on their roadmap. They are just wrapping things up with New Workfront Experience. So hopefully access to custom fields like you need or manager ID like I need will be coming later this year. :)

[#5]

I have a typeahead field called "Account Executive" on the user level. Then a user submits a request/issue. On a request/issue report, I need to show the requests including which "Account Executive" is associated with that user (request's primary contact). I am not able to get the Account Executive name to display on the report...and I'm assuming it's because of the typeahead field. Any other custom field on the user level I am able to display easily in text mode.

[#6]

We agree that if a typeahead field is on a custom form, that associated list/data of the selected object in the typeahead should dynamically auto-populate/ display into other fields in the form.

Realizing this should also be configurable by a sys admin to say which fields should auto-fill based on the typeahead result.

[#7]

We have a project custom form that includes a typeahead field with the project object. This helps us link 2 related projects together. It would be very helpful to have the ability to pull in or reference any of the custom form data for the related project.

[#8]

I can see lots of uses for this. A best practice with data management is to have the data located in one central place and then to pull that data into whatever location is needed. I like the example of pulling employee IDs or something like that into a project or report through a custom field on the user. Another example for us is when we have separate projects that have some kind of a relationship. I often have certain custom fields on one project, and I want to pull those into the second project for reference. The desire is to establish the project-to-project relationship with a typeahead field and then to pull custom data from that project into the project at hand.

[#9]

I can see lots of uses for this. A best practice with data management is to have the data located in one central place and then to pull that data into whatever location is needed. I like the example of pulling employee IDs or something like that into a project or report through a custom field on the user. Another example for us is when we have separate projects that have some kind of a relationship. I often have certain custom fields on one project, and I want to pull those into the second project for reference. The desire is to establish the project-to-project relationship with a typeahead field and then to pull custom data from that project into the project at hand.

[#10]

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.

[#11]

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.