Service Pack 40, 'UFN_REGULAREXPRESSIONMATCH'" execute permission

Matthew Handelman
Matthew Handelman
Kudos 1 Name Dropper First Anniversary Facilitator 1
in Blackbaud CRM Developer Discussions

Last night, we installed SP40 into our test environment, and now when we run the "Refresh search constituent" Global Change, we get the message "The EXECUTE permission was denied on the object 'UFN_REGULAREXPRESSIONMATCH'"

That's all OOB functionality - wondering if anyone else has installed SP40 and is seeing the same thing.

Answers

  • Alan French
    Alan French
    Tenth Anniversary Kudos 5 Name Dropper Participant

    I've just installed SP40 in our staging environment so I could give it a go - before I do, what does the global change actually do? It's not one we've run before and it doesn't seem to take any kind of parameter/selection.

  • Matthew Handelman
    Matthew Handelman
    Kudos 1 Name Dropper First Anniversary Facilitator 1

    It's an OOB GC, and it's been in one of our nightly queues long before I started working here, so I really don't know what it does.

    What's weird: we have three test environments, and we applied SP40 to all three environments. The next day, the permission on that object, and also UFN_IDSETREADER_GETRESULTS_GUID, were missing, but only in one of our three test databases - the other two are fine.

  • Alan French
    Alan French
    Tenth Anniversary Kudos 5 Name Dropper Participant

    Ah I see - I've had a look and we do have that global change set up, which was run by our BB consultant 3 years ago during the database migration process and then never again, so whatever it does, it doesn't seem to be critical! 🤣 We're currently performing UAT in Staging so I'm reluctant to run it without understanding what it does I'm afraid, in case it affects our testing. I don't see it listed in Blackbaud's manual of global change definitions either, which isn't helpful.

  • Peggy Parviainen
    Peggy Parviainen
    Tenth Anniversary Kudos 1 Name Dropper Participant

    Hi, We had an issue a while back with constituent records not being matched appropriately in batches and transactions, and the solution was to run that global change. I think it just refreshes the search functions somehow. We don't run it regularly or anything, but have a note that it's what we do if we start having problems… from our conversation, "I just wanted to update you that I think we have a solution to this issue identified and implemented. With BB’s help, we refreshed the constituent search function that is used in batch to try and match existing records.".

  • Peggy Parviainen
    Peggy Parviainen
    Tenth Anniversary Kudos 1 Name Dropper Participant

    (also, I ran it in our test environment that we've just upgraded to SP41 for testing with no issues)

Categories