Note: This was tested in both Rome and Tokyo, and I experienced the exact same behavior in both.
In building our Catalog Items, we want to add an additional Display field to show in the Reference/List Collector drop-down (for User table variables), as we sometimes have duplicate names in that table and need to differentiate them.
If I were to go to the User Table, bring up the Dictionary Entry, and update the attributes to add a pre-defined user field (like "Active"), the attribute looks like this:
the search works fine (as expected), as shown below:
However, if we decide to add a Custom Field to the list of fields shown in the drop-down, the search functionality stops working. This is what the attribute looks like:
And this is what the search look like:
Why does the Search functionality stop working if you add a Custom Field? Is there any way around it?
By the way, if I try to add the attribute right in the Catalog Item variable instead of doing it at the User table dictionary level, it still exhibits the exact same behavior.
And here is the really odd thing. If I try to apply the same logic to the Caller field on the Incident table, i.e.
It works there, as shown below:
Is there any way to do what I want on my Catalog Item user drop-down fields?
Thanks
OK, did these two steps, as shown in my original question:
[quote]A/ Add custom field to sys_user
B/ Update the sys_user collection record attribute[/quote]
I then opened an OOB Catalog Item that includes a Reference to the sys_user table. I chose the "Whitelist IP" Catalog Item. If I try to expand/filter the "Who is the primary contact?" Reference field on that form, it still exhibits the behavior I describe in my first post. I type in "J", and it does NOT filter the records and jump down to the records beginning with the letter "J" (see below):
I also tried it on the OOB "Password Reset" Catalog Item, and had the same problem.
