Hello,
I ran into this issue again last night where I needed to have an attribute that could be both assigned for Name 1 one and Name 2 with different values respectfully. But I ran into the issue where the n1n2_ind is not part of the primary key on TX_CUST_KEYWORD.
I was able to resolove my problem by setting up two sets of attributes with the same name. Then where I was using them in my custom code was able to use them by some grouping.
I was wondering why this is not part of the primary key? It makes sense that is should be when you can allow attributes to have multiple values.
Thoughts?
Thanks,
Jon