This article is relevant if you are setting email based switches in your NetSuite SuiteScript 1.0 programs.
Background
Our Content Renderer Engine (CRE) toolset has solved many challenging outbound email messaging requirements. Written before SuiteScript 2.0 was available, the application leverages the nlapiSendEmail function based on NetSuite’s Communications APIs. Recently a client needed to send emails to over 10 recipients (via cc) in a single message. Following the Help documentation, to overcome the number of recipients limitation, we modified the notifySenderOnBounce parameter to allow for a false setting in our programs.
Implications Setting notifySenderOnBounce to False
After we modified the system to allow for the false setting, we were able to add more than 10 recipients. All seemed well. However, one of our clients discovered that a number of his CRE generated emails were delayed being sent to the recipient. After a fair amount of diagnostics which included getting help from NetSuite Support, we discovered that the notifySenderOnBounce SuiteScript 1.0 parameter drives a setting to inform NetSuite to use their Bulk Email infrastructure versus their Transactional email infrastructure. See this NetSuite SuiteAnswers article for more information. When using the Bulk Email infrastructure, the timing for email delivery is queued.
SuiteScript 2.0 for NetSuite Bulk Email
The SuiteScript 2.0 API makes it clear which infrastructure to use. You can chose the email.send() versus email.sendBulk() which targets Transactional versus Bulk Email infrastructure respectively.
Always Learning in NetSuite
When our team gets together to share challenges and accomplishments, we like to say that the learning never stops when acting with NetSuite. Even after 10 years working with NetSuite, whenever I think my mental model of the NetSuite architecture is sound, sure enough, I need to refine my thinking. If you would like to work with experienced NetSuite professionals, let’s have a conversation.
