In marketing cloud, if i have a sendable data extension that relates to all subscribers by subscriber key, and the data extension also contains an email address field:

On sending, if the subscriber already exists, the email address used for sending is the one in the all subscribers and the one in the sendable data extension is not used.

Is there any way to alter this behavior? to make marketing cloud use the email address in the sendable data extension no matter is that is different from the email address in the all subscribers.

closed as off-topic by Mohith Shrivastava, Lukas Lunow, Raul, Boris Bachovski, Mr.Frodo May 9 at 13:38

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on problems in code you've written must describe the specific problem and include valid code to reproduce it. For help writing short, self-contained syntactically-valid examples, see: SSCCE.org" – Mohith Shrivastava, Lukas Lunow, Raul, Boris Bachovski, Mr.Frodo
If this question can be reworded to fit the rules in the help center, please edit the question.

  • how are you sending the email that you are experiencing the issue? User Initiated, trigger email, send wizard, journey builder? I personally have never experienced this before, so any further details into the issue you can provide the better we can assist. – Gortonington Dec 12 '17 at 13:17
  • User initiated send. It's out of the box behavior to send the email to the subscriber's email address in all subcribers. – Javier De Mauri Dec 12 '17 at 16:03
  • But if you assign the sending relationship for the new DE, you should be able to match the email addresses. E.g. EmailAddress field in DE matches Email Address field in Subscribers. This way it will send to email addresses in DE, not based off Subscriber ID or Subscriber Key values. – Gortonington Dec 12 '17 at 16:28
  • Possible duplicate of Updating All Subscribers from Data Extension – Jackson Chen Apr 16 at 20:31
  • To @Gortonington, thanks for your reply. But I actually need to use the subscriber attributes that relates to my subscriber key but just with another email address. Your solution would involve auto creating new subscribers when the email addresses are not found. Thanks also Jackson-chen, but that involves a whole bulk recurrent process to update all subs. To all: There is another solution more straightforward: theres a business rule that just needs to be activated to achieve this behavior. – Javier De Mauri Apr 22 at 11:17