carry over first name from quick find to search box

In 7.92, if you type in a first name and last name in a quick find box (or in batch find) and there is a duplicate the first name does not carry over into the search box when it pops up. This leads to double work, or makes the quick find much less useful.

  • Dave DeBoer
  • May 25 2012
  • Shipped
  • Attach files
  • Guest commented
    March 17, 2016 23:25

    This is an issue that is under evaluation. See Knowledgebase Solution
    http://www.blackbaud.com/kb/index?page=content&id=BB732340

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    I sure hope this moves from "under evaluation" to "resolved" soon.

    Entering "r anderson" and getting a results list of all the Andersons to scroll down is a pain.

    Yes, KB has alternatives for searching but so used to doing this from version 7.91. Why go backwards?

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    Adding key strokes and mouse movement reduces our efficiency in Raiser's Edge and is not a long-term alternative for a busy office. Is there an ETA on getting this fixed, Ragan?

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    The new 7.92 search algorithm has dramatically increased search times for constituent look-ups. Not being able to type in the first name in the quick-find slows down data entry staff even more. One step forward, two steps back, eh, Blackbaud?

    Attachments Open full size
  • Anonymous commented
    March 17, 2016 23:25

    This also happens in batch, when you type in last name, first name, the last name carries over to the search box, but the first name doesn't.

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    oh good, glad BB is on it. I lost a lot of search functionality i had before 7.92; the query i attached to show class yr, spouse name, & key differentiators in our multi-generational community no longer shows what i need. And is no longer one row per constituent which makes it clunky & cumbersome. ugh.

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    @Vici Wolff - if you open the constituent search window, uncheck "enhanced search" checkbox at the bottom, then click on Options, and check "Use classic search", you will be able to resume using your query for search results. Losing first name was a big facepalm moment for RE, but at least they didn't get rid of classic search.

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    Can't wait for that new patch!

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    Any progress on this patch? It really is a problem and slows things down significantly! Thanks!

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    Please fix the quick find so that if I am looking for Johnson, Mi* it, will take me to all the persons with first names that start with "M" instead of ALL persons with a last name of Johnson.

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    angela, update your Raiser's Edge to the latest version and it'll automatically fix that issue.

    Attachments Open full size
  • Guest commented
    March 17, 2016 23:25

    Angela - it has been fixed. Keep up with patches and you get the fixes. also... notice the completed flag on this suggestion.

    Attachments Open full size

Related ideas