Ensure that all characters are searchable in Webview Query criteria for table fields

Currently, when using "one of" criteria and then searching from a list of table entries, you cannot search by a special character. I have specifically tested this with Fund ID for the characters !, *, #, @, &.

In our shop, and I'm sure we're not alone, we use a special character to differentiate between certain types of funds in the Fund ID. We use # to denote an Endowed fund. Up to now, we were able to search in the query criteria fields for *# (wildcard telling you to find # somewhere in the code name) and it would bring up every endowed fund (we have around 100) making it very easy to select all Endowed funds.

Webview query cannot do this and this is a huge problem for usability. It means somethign that takes us about 30 seconds to accomplish in database view query takes 10+ minutes to accomplish in webview query. This is aside from other usability issues with the UX for the "one of" criteria and how it allows you to view and select tables entries during query set up. (I'll be creating a separate idea for this one.)

But losing the ability to use our current coding intelligently in RE is crippling to our organization and so I strongly urge Blackbaud to make all characters searchable in webview query.

  • Maya Rosman
  • Jan 17 2025
  • Shipped
Reporting and Analysis
  • Attach files
  • Karen Diener commented
    27 May 15:57

    Same as Becky Garling - came here to post this concern. And same concerns as Sunshine.

    Attachments Open full size
  • Becky Garling commented
    27 May 15:47

    @David Springer: when I use the "one of" operator, adding the "%" wildcard results in "no matches found."

    Attachments Open full size
  • Sunshine Reinken Watson commented
    27 May 15:45

    After a quick test, % works for me for fund description, though it is going to take a lot of muscle memory retraining to stop using an asterisk. This wildcard IS NOT working for other fields using "one of," such as constituency codes and custom field descriptions. Will it be rolled out in other areas?

    Attachments Open full size
  • Admin
    David Springer commented
    27 May 14:35

    Hi all! Web view query supports % as a wildcard, so in Maya's examples above, you'd search for %# instead of *# to return any fund with # in its ID.

    We've now called this out in our help documentation, which will hopefully make it easier for other users to find.

    image.png
    Attachments Open full size
  • Karen Diener commented
    22 May 14:08

    Wildcard searching is imperative and used every day. Yet another reason that adoption may be low - it is not a frictionless process.

    Attachments Open full size
  • Spring Velazquez commented
    17 Jan 23:50
    Either enable wild cards OR improve the search functionality. Google it is not!
    Attachments Open full size
  • Sara Hassell commented
    17 Jan 18:23

    Please ensure that all characters are searchable in Webview Query criteria for table fields. Organizations often use special characters for funds.

    Attachments Open full size
  • +67

Related ideas