I would like to create a field that functions like the Assignments field on the Task object, so that I can associate some people with tasks without formally assigning them. But when I create a Typeahead field using User as the Referenced Object Type it is single-entry and I cannot find any way to change that.
Topics help categorize Community content and increase your ability to discover relevant content.
Not yet James, as per this related thread.
If you have a finite set of users in mind (unlikely, since you're trying to use type ahead) you might consider using a multi-select drop down with one entry per person (and -- bonus marks -- using their GUID as the value in the drop down so you can do other cool $$USER.ID things with it),.
Regards,
Doug
@Kyna Baker - inactive‚ to find that previous thread, recalling that in Classic Community that I'd put an image of a silver bullet cartoon on my post (and mentioned that in the text), I tried your tip from yesterday and searched in 0ne for "silver AND bullet" (meaning I needed both terms in the post), and presto! Two hits matched, and the first one was the one I wanted. I will definitely keep using AND in my searching -- thanks for pointing it out!
I was wondering about this also.....@Doug Den Hoed‚ I understand the multi-select dropdown but I don't understand what the rest means lol ....what do those name options look like in form with GUIDs?
we have a "stakeholders" field that I had to leave as a text ---but when there are several names I was hoping type-ahead might solve for that....would still need another text field to account for non-users.
Views
Replies
Total Likes
Hi Tegwyn,
End users will still see the user names in the multi-select dropdown (as the "label"), but under the hood, it will in fact be the user IDs that are stored (as the "value"), which in this case, is the best of both worlds, since you can then do some cool stuff with the currently logged in $$USER.ID (e.g. filtering, conditional formatting, etc.)
This post has more details on how to configure a multi-select dropdown to show user names (as labels) and store user IDs (as values).
Regards,
Doug
Views
Replies
Total Likes
Hi Doug, I have this exact problem today for a new instance. We're not yet using tasks and have a multi-select dropdown to identify one or more assigned individuals. I've followed this thread to use the user ID as a value and the name as a label. But I'm not sure what to do next with the multiple user IDs in my field. How do I take a string of multiple IDs and then match them back to user profiles? The thread you had helpfully linked to is no longer available.
Views
Replies
Total Likes
Hi @JessicaCh,
When I saw your note, I asked @jon_chen to restore my old articles, but see the one you'd mentioned still isn't available. Once it is, Jon, please tag Jessica and me so we can see if it does the trick for her.
Regards,
Doug
Views
Replies
Total Likes
Thanks, Doug! I actually took another shot at this one, and re-discovered that I can go into text mode to tweak the filters. It was surprisingly easy to use contains $$User.ID and it's working like a dream! Always appreciate all of your help, and can't wait to have your old articles to fall back on, so I can continue to learn.
Views
Replies
Total Likes
My pleasure @JessicaCh,
Yep: that's the whole trick (using $$USER.ID to return the logged in user's relevant data). Glad you got it going!
Regards,
Doug
Views
Replies
Total Likes
Noted @Doug_Den_Hoed__AtAppStore @JessicaCh! I will follow up on this thread once the articles have been restored. Thanks for your patience.
Views
Replies
Total Likes
@Doug Den Hoed‚ Thank you! I get it...we use this for cost centers....users just see the name but the code attached in underneath!
this is great info, I knew those codes carried over but never thought about using in this way!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies