mynt

module function · N/render

mergeEmail()

render.mergeEmail(options)

Creates a render.EmailMergeResult object.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
render.mergeEmail(options)
Module
N/render
Returns
render.EmailMergeResult
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1render.mergeEmail({2    templateId:    /* number, required */,3    entity:        /* RecordRef, optional */,4    recipient:     /* RecordRef */,5    customRecord:  /* RecordRef, optional */,6    supportCaseId: /* number, optional */,7    transactionId: /* number, optional */8});
Oracle reference for this method
ParameterTypeRequiredDescription
options.templateIdnumberrequiredInternal ID of the template.
options.entityRecordRefoptionalThe entity.
options.recipientRecordRefThe recipient.
options.customRecordRecordRefoptionalThe custom record.
options.supportCaseIdnumberoptionalThe support case ID.
options.transactionIdnumberoptionalThe transaction ID.
B mynt syntax

No Mynt syntax yet.

Nothing in the language compiles to render.mergeEmail(options) today. How should it read?

C community proposals

Competing syntax for mergeEmail, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D suggest an alternative

Write the Mynt you wish you could write.

A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.

  • Clarity. Does it say what happens, without ceremony?
  • Consistency. Does it read like load, save and Ref[field]?
  • Expressiveness. Does it cover the cases people actually write?
  • Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?

N/render · render.mergeEmail(options)

Suggest syntax for mergeEmail