Skip to main content
User Experience

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • The data isn't duplicated. It comes back in the form of { firstname: 'John', lastname: 'Smith', groups: ['Finance', 'Sales'] } Commented Aug 12, 2019 at 8:33
  • Even better. Since it's a single record that's being split on the front-end, type-ahead should be able to run on the single-source list that's feeding into the front-end, instead of the split up list made by the front-end. Commented Aug 12, 2019 at 16:01
  • I'm afraid you've lost me. Previously, users were only part of one group. So it was as simple as having a categorized select list, where you can select both the group and the users below it. Now however, with users being in multiple groups, when you start typing a user's name, they could come up under multiple groups, which will be confusing for the end user. Commented Aug 13, 2019 at 9:38
  • But the source of that list does not have duplicates. It's one person (John Smith), who has then been replicated and put into two groups on the front-end. But an array exists of just the unique individuals. Your type-ahead should be able to run the search on that source array, not the content on the front-end, and display the unique results from the source array. Commented Aug 13, 2019 at 16:00