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
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!