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.