TemplateRenderer object method · N/render

addRecord()

TemplateRenderer.addRecord(options)

Binds a record to a template variable.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
TemplateRenderer.addRecord(options)
Module
N/render
Returns
void
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1objTemplateRenderer.addRecord({2    templateName: /* string, required */,3    record:       /* record.Record object, required */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.templateNamestringrequiredName of the record object variable referred to in the template.
options.recordrecord.Record objectrequiredThe record to add.
B

No Mynt syntax yet.

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

C

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

All discussions

Loading proposals from GitHub…

D

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 · TemplateRenderer.addRecord(options)

Suggest syntax for addRecord