Search constituent doesn't return lookup_id for search_field=email_address

Harry Bailey
Harry Bailey
Third Anniversary Facilitator 1 Boomerang (2024)
in Blackbaud Raiser's Edge NXT® APIs

Although the documentation suggests that lookup_id is always returned for a search, when you use search_field=email_address the lookup_id is missing.

It is included for search_field=lookup_id and it is included for a search without the search_field attribute.

I'm assuming that's a bug, but it means you can't use the “faster” search_field=email_address if you need to know the lookup_id without an additional request.

Search result entity from docs showing lookup_id:
https://developer.blackbaud.com/skyapi/renxt/constituent/entities#SearchResult

Comments

  • Anthony Gallo
    Anthony Gallo Blackbaud Employee
    Tenth Anniversary Kudos 5 Commented in Discussion First Reply

    @Harry Bailey

    This search option used to only run off of lookup ID so there was no reason for us to return that data in the call. We have since updated it to allow for email address and we missed updating the return results to return that ID. We will create a task on our side to get that added as soon as we can.

    We have a major lists project going on so we will gain performance improvements when that project wraps up in Q2 of 2023.

  • Harry Bailey
    Harry Bailey
    Third Anniversary Facilitator 1 Boomerang (2024)

    @Anthony Gallo
    Thanks. Ironically, any other search, including search_field=lookup_id does return a lookup_id

  • Steven Cinquegrana
    Steven Cinquegrana
    Tenth Anniversary Kudos 2 Name Dropper Participant

    @Anthony Gallo If there's a chance that the (immutable) Record ID will ever be used in other calls, would it be prudent to add that into the response as well?

Categories