๐Ÿ‘€ Want to skip this article and just see proper email addresses of the sender/recipient? Skip to the 'View tips' tips section and implement the suggested change to your view.

Still interested in the technical reasons behind why a sender/recipient NetSuite entity might seem different? Read on....

Technical Discussion

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

Author Entity
Author Email
Recipient Entity
Recipient Email

Under normal circumstances users attach emails to NetSuite 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 if you are manually attaching an 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).

CloudExtend Behavior

To ensure that your email is not rejected by NetSuite CloudExtend may need to set the sender or recipient as a known entity. Fortunately CloudExtend is able to overwrite the email address which is why we recommend implementing the view tips and just moving on.

  • The sender or recipient may show a different name if the sender/recipient is not a contact under the NetSuite record you are attaching to. NetSuite requires that the sender/recipient of the email you are attaching is also listed as a contact (in the case of attaching to an entity record).

    • For example, joe@xzy.com sends you an email and you attach the mail to a customer record and Joe is not also a contact for that customer record. In such a case CloudExtend needs to set the sender as the customer in order to ensure NetSuite does not reject the mail. CloudExtend can, however override the email address and set it as joe@xyz.com. This is why we simply recommend implementing the view tips and just moving on.

  • If your messages are on Autopilot the behavior is different than below. See this section for more info.

Behavior 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.

Below is a way to visualize this in NetSuite. If you open a customer record and then compose a new email you will see that the recipient list is restricted only to those contacts of the company. ย The Netsuite API enforces this same rule and therefore the email attached by CloudExtend would fail. In order to ensure that CloudExtend attaches the email successfully the App sets the entity to that of the record it's being attached to. Since the NetSuite API does allow an override of the actual email address the App does send over the proper email.

Behavior 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.

Emails on Autopilot

Because emails on Autopilot are attached via a background process CloudExtend may not always have access to the same email details as if the user were manually attaching an email. The attach behavior varies depending on the record type the email was attached to.

๐Ÿ‘€ We highly recommend that you customize your view settings as per below, The email address of the sender and recipient should be used for the best visibility as to the sender and recipient.

When no matching NetSuite records are found

If no matching NetSuite records are found with the sender or recipient email (or they are inactive) then NetSuite defaults Sender/Recipient fields to the Admin that configured Autopilot (because their token/secret is used for logging in to NetSuite).

Attaching to entity records with Autopilot

If the message is attached to an entity record the following logic takes place to set the author and recipient fields.

  • The author field is set to the 1st record found when matching the following records with the sender's email.
    Below preference order is followed in case of multiple matches.
    Employee > Contact > Customer > Vendor > Partner >Job

  • The recipient is set as the entity the message is attached to.

Attaching to activity or transaction records with Autopilot

If the message is attached to an activity or a transaction the following logic takes place to set the author and recipient fields.

  • The author field is set to the 1st record found when matching the following records with the sender's email.

    Below preference order is followed in case of multiple matches.
    Employee > Contact > Customer > Vendor > Partner >Job

  • The recipient field is set to the 1st record found when matching the following records with the recipient's email. In the case of multiple recipients, autopilot uses the first recipient returned by Gmail API for record search.
    Below preference order is followed in case of multiple matches.
    Employee > Contact > Customer > Vendor > Partner >Job

View Tips

The default view of the message record does not show the Author's email. Customize your default view and add

  • Author Email

  • To

This will then allow you to work with email addresses rather than entity names. If desired remove the Author and Primary Recipient to free up space.

Did this answer your question?