Is there a way to mark a constituent record in Tessitura NOT to show up in a search at all?
Thanks!
Hi Sabina,
I'm just curious as to why you would like this record not to be returned. Is it that the constituent record should be hidden from all users (except, perhaps, system admins)?
If this is the case, you could always create an entry in the TR_CONSTITUENT_PROTECTION_TYPE table that is control grouped so that only system admins have access to and apply this to the constituent record.
Martin
It was a request from the Box Office - is there a way to suppress some records from displaying in search results? I don't know why
Thanks for your suggestion.
Sabina
Sabina,
I guess without knowing the logic behind the request, it's difficult to off a solution. I don't believe there's a way of marking records to be excluded from the Constituent Search screen and leaving the record available for use.
Martin, here is the reason:
"
The reason this came up is because a patron called and 2 accounts came up with the same name. I asked about the addresses and he said “My Dad died 10 years ago… I really wish you all would remove his information.”
I went to do that and saw that it had already been inactivated and the patron was marked deceased. There is no way to know that though when you are looking at the constituent search… and I just think it makes people sad. This isn’t the first time this has happened when I’ve had someone on the phone."
If the patron is inactive, the pawn icon in the search result should appear gray instead of blue.
Would be nice to have a "show inactive" check box like other lists in the system where you can hide those unwanted/unused items.
I was going to say "just check the Show Inactives" checkbox, which I was certain existed, but it doesn't. Wouldn't help us either: inactivating deceased constituents has caused us no end of grief, as we often need to make adjustments to their records in the year or so after they pass, nor do we want them to vanish from historical reporting, so we don't do it (we always screen on deceased for communications lists). I'm kind of shocked that there isn't a filter or visual way of telling if a customer is deceased, in fact that information isn't even available in the standard constituent header.
You could make a header item that flashes or warns you when it comes up. This would entail a custom header though.
Could, but we've kind of maxed out our flex headers already. And it doesn't solve the use case, where you're trying to figure out who the caller is from the search results.
One workaround would be to override the "Alias/Sort Name" column for deceased customers, which would be more or less visible depending on how heavily the column is used at your organization.
Could you use the “Enhanced Constituent Search” plugin (https://www.tessituranetwork.com/en/Files/Shared-Reports/Enhanced-Constituent-Search), along with a bit of tweaking? We’ve installed it here at the ROH, and I’ve already altered it so that we can search for someone’s Twitter handle (stored as a new eAddress Type) if required.
You could alter the plugin to recognise a new flag (say “InAct|” for “filter Inactive Reason” which accepts the Inactive Reason ID), and then alter the replacement SP that the plugin calls (LP_CUST_SEARCH_NEW) so that all “Inactive Reason = {supplied Reason ID}” records are by default filtered out, unless the flag has been set…
Steve
Thank you!