Skip to main content
8 events
when toggle format what by license comment
Oct 29, 2018 at 20:40 comment added Rocky Matthew: We do have (unfortunately) many cases where the same email address is associated with more than one subscriber key. Gortonington: Changing the order didn't help; but as you say, I have experienced fixing an SFMC SQL error by changing an order like that where in normal SQL it wouldn't matter. Thanks, both.
Oct 29, 2018 at 19:30 comment added Gortonington @Rocky -But with Update it is an ADD/Update action, which means if the email comes up again with a different subkey, it will overwrite the previous subkey value with the new one. I doubt the following will do a thing, but in your query, try using SELECT pc.EmailAddress as Email, pc.SubscriberKey and see if the order makes any difference (it really shouldn't, but I have seen stranger things in SFMC.
Oct 29, 2018 at 18:29 comment added Matthew Wash Maybe I'm misunderstanding - if your email is set as the primary key in your data extension, but you're also selecting Subscriber Key, it's possible you are trying to enter two records with the same Email Address but different subscriber keys. You can test this by creating a different data extension that doesn't have a primary key rule, put your SELECT results there, and see where your duplicates are.
Oct 29, 2018 at 18:23 comment added Rocky Hi Matthew, I'm sorry but I'm not following. If Email is the primary key, shouldn't the query update the DE when a matching (i.e., duplicate) Email is found?
Oct 29, 2018 at 18:10 comment added Matthew Wash Well that could certainly do it. You may have a case where you have duplicate emails but separate subscriber keys.
Oct 29, 2018 at 15:16 comment added Matthew Wash What's your key field?
Oct 29, 2018 at 14:58 comment added Rocky Thank you, Matthew, for the suggestion but unfortunately that didn't fix it.
Oct 29, 2018 at 14:09 history answered Matthew Wash CC BY-SA 4.0