Hello!
I'm hoping someone has wrangled this procedure in the past and can help me troubleshoot - it appears that it's stopped running. In the recent past it ran each time a constituent record was updated - which was less than ideal in many ways - and along the way called another procedure which cleaned up any name and address data entry messes so that the contact information conforms to our consortium data standard.
In doing some related digging this week, I've found that it seems to be neither updating rank nor calling the cleanup function at the expected time. In looking at the trigger on T_CUSTOMER, as well as the code for LP_CUSTOMER_RANK, I don't see anything obvious that would be stopping it.
I should also note that I can't get LP_CUSTOMER_RANK to do what it should (update rank, at a minimum, plus call the other function) even when manually executing it through SSMS.
Any ideas where I should start?
Thanks!
Stacey Voigt
svoigt@granadasb.org
Since LP_CUSTOMER_RANK is designed for custom code, I would suspect that something has changed with the custom code or data structures they rely on that is causing it to fail. Since it is connected to a trigger on pretty much any update to a customer record, LP_CUSTOMER_RANK scripts should generally be designed to fail silently, so you should probably troubleshoot the code in question in isolation to the procedure.
This is assuming you haven't been able to conclude via logs or traces that LP_CUSTOMER_RANK absolutely isn't firing. In that case I'd suggest a TASK ticket.