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
A
suitescript api
1objTemplateRenderer.addRecord({2 templateName: /* string, required */,3 record: /* record.Record object, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.templateName | string | required | Name of the record object variable referred to in the template. |
| options.record | record.Record object | required | The record to add. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to TemplateRenderer.addRecord(options) today. How should it read?
C
community proposals
Competing syntax for addRecord, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?