Under normal circumstances users attach emails to NetSuite entity records that already have the sender or recipient's email address associated with them, i.e. if joe@xyz.com sends you an email you would attach it to his contact record in NetSuite. In those cases CloudExtend and NetSuite work as expected.

This article is meant to cover what happens in the uncommon situation of trying to attach an email to a NetSuite entity unrelated to the sender or recipient, i.e. if joe@xzy.com sends you an email and you attach it to your own contact record (or some other entity record).

NetSuite requires that four values be set when saving an email.

Author Entity
Author Email
Recipient Entity
Recipient Email

In certain outlier cases one of the required entity fields may not be able to be set by NetSuite. For example, if a user sends an email and attaches it to their own Contact record NetSuite will not be able to resolve the recipient entity since it does not exist on the Contact record (try this for yourself by going to a NetSuite contact record and trying to send the email to someone unrelated to the Contact).

For outbound emails
When attaching to a NetSuite record where the recipient's email address is not found on the record being attached to, NetSuite would normally not allow the email to attach. CloudExtend works around this limitation by attaching the email with the current entity 'name' as the recipient and replacing the email address with the actual email address of the recipient from the sent email.

For inbound emails
When attaching to a NetSuite record where the sender's email address is not found on the record being attached to, NetSuite would normally not allow the email to attach. CloudExtend works around this limitation by attaching the email with the current entity 'name' as the sender replacing the email address with the actual email address of the sender.

Did this answer your question?