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
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
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!
From: Kevin Sheehan <bounce-kevinsheehan4372@tessituranetwork.com>Sent: 5/5/2011 4:02:06 PM
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
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.