Hey folks,
I've been tinkering with writing a local procedure to populate some default values for new consitiuents, but i really don't want to run a procedure at high frequency, and even so...its just not looking like the way to go...So i went for a coffee and thought about it;
I then found TG_CUSTOMER_INSERT, and in a few minutes i was done! But, is there anything wrong with this? It'll probably get screwed up on version updates huh? Is there a better way?
I thought of calling another LP from LP_CUSTOMER_RANK, but that is only called on TG_CUSTOMER_UPDATE, not necessarily INSERT...which may be fine, but might not...On second thought, it wouldn't really work because if a keyword is unchecked, it is removed from TX_CUST_TKW, so you couldn't really see if someone unchecked it.
Thoughts? Anyone?
Thanks
James
I think the stock answer will be "don't edit triggers written by Tessitura". (pretty sure I asked this a few years ago).
As for the last bit, I don't think that the record is removed from TX_CUST_TKW when you uncheck the interest. So you can definitely see if its been unchecked. In fact, we have a list builder item (not sure if its a stock one or custom) which addresses this. So we can get a list of people who *used to* have an interest checked.
Thanks Levi!
Thats pretty much what i figured....what about making a LTG_customer_insert? Would that fall under the standard practices for Local Customizations? I'm not all that familiar with triggers, so i don't know know if you can really have 2 triggers for Insert...but i don't really see why not.
It really is not supported to change exiting triggers or add additional triggers to application tables. With the existing framework for local procedures, support has an easy way to disable the customizations if there is a problem in order to see if the customization is the cause. If you start adding triggers, we don't have this ability and support becomes very difficult.
On the positive side, starting with version 11 you will have the ability to create service plug in code that will essentially do the same thing with a lot more flexibility and granularity.
In the meantime you can use LP_CUSTOMER_RANK--it is called with when a new constituent is added as well.
Interest rows are removed from TX_CUST_TKW when the Selected box is unchecked, unless the row has a weight value. In the past if the box was unchecked through the Web API it did not delete the row, but that was corrected to be consistent with changes made through the application in v10 (possibly v9).
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Thank You, and Thank You!!!
Kevin, i though i was crazy for a second, but didn't want to double check :) I swore they were removed!
Chuck, that answers that! I didn't know LP_Customer_rank was called on insert as well as update, so for now, that will work perfectly!
Thanks again!
Just another piece of advice, make sure that you optimize anything added in LP_CUSTOMER_RANK, as this does get called often (as you can imagine)! It can easily impact performance in all areas.
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of James BoncekSent: Thursday, May 05, 2011 5:07 PMTo: Ryan CrepsSubject: RE: [Tessitura Technical Forum] Customizing TG_CUSTOMER_INSERT
From: Kevin Sheehan <bounce-kevinsheehan4372@tessituranetwork.com>Sent: 5/5/2011 4:02:06 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thanks again for the input from everyone. I implemented a good solution today;
Essentially, I/we choose to use interests as the tool for E-Mail Preference Management. I created a few preferences TR_TKW, and when a constituent is created, i insert a Selected TKW, with a weight of 1 into TX_CUST_TKW.
As this is in LP_CUSTOMER_RANK, and called on every update, i really only want to do this on creation, so...the added weight means that it won't dissappear if the person opts out. and i only check to see if the tkw exists for that customer_no before inserting. If it DOES exist, then the LP does nothing, otherwise, it creates it.