mynt

TemplateRenderer object method · N/render

addCustomDataSource()

TemplateRenderer.addCustomDataSource(options)

Adds an XML file or JSON object to an advanced template as a custom data source.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
TemplateRenderer.addCustomDataSource(options)
Module
N/render
Returns
void
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2016.1
call shapefrom Oracle's parameter table
1objTemplateRenderer.addCustomDataSource({2    alias:  /* string, required */,3    format: /* render.DataSource, required */,4    data:   /* Object | Document | string, required */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.aliasstringrequiredData source alias
options.formatrender.DataSourcerequiredData format
options.dataObject | Document | stringrequiredObject, document, or string
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for addCustomDataSource, 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 · TemplateRenderer.addCustomDataSource(options)

Suggest syntax for addCustomDataSource