Refine search by constituent ID to match only exact digits entered

When we search for constituent 711 the results pull 1711, 10711, 11711, 12711, 13711, 17111, 17112 etc. We have thousands of records like many orgs. This makes search by ID # useless as 711 appears on page X . Same issue in query on db side.

  • JoAnn Strommen
  • Feb 18 2021
  • Reviewed: Voting Open
  • Attach files
  • Amelia Ketzle commented
    May 13, 2025 14:28

    This is a common problem for us, too. Especially when the Constituent ID is only a few numbers and the name is relatively common, there is no good way to find such a constituent. From the home search bar, you can hit 'Enter' and see a list of all matches, which works (although an 'exact' match should be an option on that home search bar), but if you're trying to pull such a constituent into a relationship search, that functionality isn't even there. I had to go search for the person from the home search bar, then find an Alias on their record that would be relatively unique and use that to find them for the relationship search. Too many steps.

  • Greg McKnight commented
    July 13, 2022 21:09

    We have noticed the alias may contain that same # as the constituent ID you're searching, and that the list of #s that match (in whole or part) as an alias trump the constituent ID in the results list and appear first. You have to scroll through several screens just to find the "711" record you wanted.