Is there a way to identify the correct lookup value when the name is not unique or is there a specific order the results return?
In some use cases I expect that the name may not be unique unless this is enforced upon record creation.
Identify correct Lookup Record when there are duplicate Names
This is a tough one, especially since each custom object structure is unique. With the search APIs integrated, the results will be sorted based on relevance. However, if the records are nearly identical - what would help your agents make that decision? Any recommendations there?
Thanks @thomas verschoren12 - We did think about this option.. However, our concern was the lack of standardized experience across all objects there.. The only other standard field is the external ID (which wouldn't be visually pleasing and wouldnt help solve the problem). Let me work with my design and see how this can be solved..
We do plan to make all text fields in a custom object searchable pretty soon.. The team is already working towards it.. Hope this would enable a better experience.
Love the idea.. That was my initial thought as well.. However, we'd have to consider a few additional things:
1) Educating users that the 2 that you see right under search experience is infact the Pokedex Number OR show the field name there (which would be crowded from an experience standpoint)..
2) Key details customization will potentially not be available for plans.. This is an easy problem to solve if we go this route.
CC: @Nicolette Robichaud
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.