Hello Community,
While working with Employee Center search, I’ve noticed that achieving consistent alphabetical (A–Z) sorting across results is not as straightforward as it might appear, particularly when translated fields, relevance ranking, and multiple search sources are involved.
In practice, search results often prioritize relevance and indexing behavior over strict alphabetical order, which can be confusing when configuration options appear to allow sorting by fields like Title or Name. This seems especially noticeable when those fields are translated or derived from referenced data.
From an architectural standpoint, I’m interested in how others approach this:
Do you intentionally rely on relevance-based ranking over alphabetical ordering in Employee Center?
How do you set expectations with stakeholders who expect deterministic A–Z behavior?
Have you implemented any patterns naming conventions, non-translated sort fields, content design that work well without introducing upgrade risk?
Looking forward to hearing how others balance search experience, platform constraints, and user expectations.
*Please give a Thumbs Up if you find this Helpful!!
