Hi all,
In the What’s new in V11 doc it talks about LP_CUSTOMER_RANK causing problems with the new services layer and offer 2 solutions. I took the easy one which was adding a couple of lines of code at the beginning and end of LP_CUSTOMER_RANK and this seemed to take care of the issues we were having when updating account info. Now however….the errors have come back! Nothing has changed in LP_CUSTOMER_RANK.
My only thought is to tackle the second solution which is:
“move logic from LP_CUSTOMER_RANK into service interceptors where you have more fine-grained control over when changes will be made”
I have no idea what this actually means and can’t find anything other than to-be conference presentations (I know what I’ll be attending :) ) that makes reference to this. I had a look in TIM and the have also found the Tessitura.Services.Plugin.Examples but not too sure how any of it works. Where would I be moving the logic to exactly? Has anyone else had to do this?
Thanks for any advice!
While you can do most anything that was possible in LP_CUSTOMER_RANK with a service interceptor, it certainly should not be necessary to convert your existing procedure code to an interceptor to make it work in v11. If the suggested additions to LP_CUSTOMER_RANK which were recommended for v11 did not fix the problem you were first having, I would suggest opening a help ticket for this.
Hi Chuck,
I just saw you post after I sent my last one. I'll open a ticket.
Jon I would still be interested in your examples if that's OK as I'm sure that it is something I may have to do in the future and I'm rather interested to see how the new services layer can be customized as such.
Thank you both for your help.
Sure I would be happy to go over what I have done with them.