How can I easily show only unique values in a List Collector?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2016 01:49 PM
I am wondering if there is an easy straight-forward way to show only unique values in a List Collector.
I have a table that contains mappings between our internal Applications and the Countries in which they are available. Consider this example:
| Application | Country |
|---|---|
| Internal Application 1 | USA |
| Internal Application 1 | France |
| Internal Application 1 | Germany |
| Internal Application 2 | USA |
I need to display only unique Application names in a List Collector. I have set the appropriate display column in the source table and associated the table to the List Collector, but when I view the List Collector I see:
Internal Application 1
Internal Application 1
Internal Application 1
Internal Application 2
How can I eliminate the duplicates? Can this be done with reference qualifiers somehow? I've searched online and have found very little on this topic. Thank you in advance if you are able to steer me in the right direction!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2016 01:51 PM
A list collector is going to show whatever's in the table. Is the table you're selecting from an M2M, even though you intend for a user only to select 1 side of the M2M relationship? This sounds like a data structure problem more than an interface one. That is to say, you mean for users to pick an Application... not a relationship between an application and a country.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2016 02:15 PM
It's just a stand alone table that contains for the most part a column of application sys_id's and another column of associated country sys_id's (there are no mapping tables involved).
Actually I ultimately what I need is in fact for users to pick an application and country relationship. That would be ideal! But back to the List Collector... I am not aware of a way to present that combined information to the user. If I could have the List Collector show something like this (and return the sys_id of the source table record) my problems would be solved:
Internal Application 1 (USA)
Internal Application 1 (France)
Internal Application 1 (Germany)
Internal Application 2 (USA)
