- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2017 07:17 AM
I have some List Collectors on catalog items that reference a user table. Many users have the same name, so when they type the name and select one, they wont know if they have selected the right person or not. This was not a problem in the old catalog because OOTB when you selected their name, it would show additional details beneath the list collector.
The only way I can think to fix this would be to do something like add an onChange client script that populates a read only string field beneath the list collector, which could populate a unique identifier (like their email address) for the selection.
Is there a better alternative to fix this problem?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2017 07:44 AM
We had a similar situation where we had a list collector for Applications users could choose. The portal doesn't show details like the OOTB ITIL view does so I did the following:
- Created a new hidden Reference field called "Last App Name" and pointed it to our Application List table
- Wrote an onChange client script to write the last app chosen in the list collector array to this hidden "Last App Name" field
- Created a new Single Line Text field called "Application Details"
- Then wrote another onChange client script to pull the "Description" column from our Application List table for the app in the "Last App Name" field and write the description to the "Application Details" field which is a read only field through UI policy.
So basically if they choose 1 or multiple apps...the description for the last one chosen is shown in the "Application Details" field. Obviously you could do the same thing for users and write the email or whatever to the read only details field. You may not even need the first onChange, but using a list collector they may choose multiple people so might be best. Also, I just added the application description, but you could get multiple fields if needed and write them to a multi line text box too after combining them together. All kinds of things you can do once you get it working with 1 field.
Please mark this response as correct and/or helpful if it assisted you with your question.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2017 03:31 PM
Hey all,
If you're still struggling with this issue, you may want to have a look at the Yansa Design System. We've included an enhancement to allow the display of additional fields for Reference & List Collector variables in Service Catalog. This allows you to more easily differentiate between similar records, as well as searching against those additional fields via typeahead.
http://www.yansa.io/yds/#catalog_item_widget_yds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2018 03:34 AM
We have this same issue with user records . lots of users with same name. what did other do outside of using a external solution ?