I have to assume my discovery is by design.
If I create an entry in "T_KWCODED_VALUES" and specify a value for the "key_value" field, then refer to that value by assigning it to a customer within the "TX_CUST_KEYWORD" table, then change the original value of the "key_value" field in "T_KWCODED_VALUES", then the "key_value" field in "TX_CUST_KEYWORD" is not automatically updated to match the modified value.
I am wondering how this is typically handled? I am building some custom web code, and I want to join these two tables with the join clause partially conditioned by the "key_value" field. But if I go into the T_KWCODED_VALUES table and change the value, then the attributes on the customer are not automatically updated, and so my join "breaks".
Is there a better way to do this?
Thanks!
I built a SQL update trigger for the T_KWCODED_VALUES table to enforce the referential integrity. If anyone's interested, ping back and I'll forward.
Hi Larry -
Is this something that you've put on the t_kwcoded_value table itself? If so, just watch out for Tessi updates which *could* overwrite/drop and recreate the table/etc.
Other than that, sounds like a great idea. Would you mind posting the sql to your profile for sharing?
Heather
Yes, that's the table the trigger is on. I've named it LT_T_KWCODED_VALUES_RefUpd_TX_CUST_KEYWORD
LT_T_KWCODED_VALUES_RefUpd_TX_CUST_KEYWORD
"LT" for "local trigger".