Limit Items displayed for a Type-Ahead field

[#1]

Currently we use a type-ahead field for our users to locate an existing Campaign. We renamed the object Program to Campaign. If you look in the Overview section of a project, you can only search for those programs that are associated to a particular portfolio. Unfortunately, that logic is not carried through for other searching. When a requestor makes a request, we ask if there is an existing campaign and if there is we ask them to use a type ahead search to locate the campaign. Since there is no logic within the request process to filter only on those campaigns associated to a specific portfolio there is a higher possibility for the user to select the wrong campaign. We would also like a way to limit the search of a type-ahead on only active campaigns, today you can pick a campaign that was created 5 years ago. Please reference support case 00426130.

[#2]

Hi @cathycr1  - I did want to let you know that you can apply filters to a typeahead field. They only take text mode at the moment so my little hack is to do a report with that same object type (in your case a program), do the filters the way you'd like them, switch to text mode, and then copy and paste that text mode into the filter for the typeahead field. 

Now, in the screenshot above, I hardcoded the portfolioID. It you are looking for something that is a little more flexible, you might want to take a look at the newer External Lookup field. It is kind of like a typeahead field but it is more flexible as it just uses an API call to get the info you want. It can also reference information you already have in your form. So you could have them select a portfolio in the request form and then have the external lookup field show you the active programs for that portfolio. (Let me know if you are interested in that. That has a lot of steps so want to make sure that is what you want before I dive into that )

NOTE: One thing though with the External Lookup field, with it being a newer type field, there are some issues with it that I'd want you to be aware of:

1. It saves the information on the object as text, not a choice. So when you are looking to do prompts or filters on reports, you have to type in the info like it was a text field, not a choice field
2. You can't get additional info like ID or other OOTB fields like you can with a typeahead field
3. You can't in-line edit the field in dashboard or report currently. 

Now... I do believe all of this should be a lot easier through the interface and with the typeahead field type, so I think your idea is still very valid. But wanted you to know there are some options while you are waiting for that day