Typeahead fields Status on Roadmap | Community
Skip to main content
C
ChrisRo9
May 2, 2024
Solved

Typeahead fields Status on Roadmap

  • May 2, 2024
  • 2 replies
  • 1801 views

Does anybody know if typeahead custom fields to be able to pick users are on the roadmap? Where would anyone be able to see if they are likely to be introduced?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by VicSellers

    Hi @chrisro9 - Typeahead fields for users are currently available!

     

     

    2 replies

    VicSellers
    Community Advisor
    VicSellersCommunity AdvisorAccepted solution
    Community Advisor
    May 2, 2024

    Hi @chrisro9 - Typeahead fields for users are currently available!

     

     

    C
    ChrisRo9Author
    May 3, 2024

    Thank you Victoria,

     

    I found it in the new form designer section. Whilst it only allows one selected user it will solve my problem for now, would be great in the future if multiple users could be selected in that box.

    skyehansen
    Community Advisor
    skyehansenCommunity Advisor
    Community Advisor
    May 6, 2024

    Sounds like you're looking for a way to select multiple users, and I wonder if you've considered exploring external lookup fields to see if you could use them to get this working. (by the way I recommend using email addresses rather than user names if viable... this way if you pull up two John Smiths, you don't have to guess.)

    https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/customize/custom-forms/form-designer/design-a-form/external-lookup-examples

    C
    ChrisRo9Author
    May 7, 2024

    Hi Skye

     

    Thank you for this, this looks like it would solve the problem completely, do you happen to have an example of the base API URL that would get me to users and then the JSON Path?

     

    Thanks 

     

    Chris

    skyehansen
    Community Advisor
    skyehansenCommunity Advisor
    Community Advisor
    May 7, 2024

    could you try variating the example given and then come back and walk us through what error you might be seeing?

     

    I would say for json, experiment with the "$.data[*].name" that they show you, or maybe try $.data[*].emailAddr if you decide to use the email address as I suggested?

     

    For the base API -- again, play around. The example given was "$$HOST/attask/api/v15.0/project/search?status={DE:StatusQuery}&$$QUERY"

     

    * Could you switch out the "project" object for "user"?

    * Instead of searching on "status={DE:StatusQuery}" maybe search on "isActive=true"? What are some of the other user attributes you might want to search on? (e.g. reports to a certain manager, belongs in a certain home team or home group - these are all simpler parameters you could try and link up with the ampersand symbol, and they would be easy to get from a user report filter; just build in there and switch to text mode)

     

    Terms & ConditionsAccessibility statement

    Loading footer...