mynt

TemplateRenderer object method · N/render

addQuery()

TemplateRenderer.addQuery(options)

Uses Query as the renderer's data source.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
TemplateRenderer.addQuery(options)
Module
N/render
Returns
void
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2019.2
call shapefrom Oracle's parameter table
1objTemplateRenderer.addQuery({2    id:           /* string */,3    pageIndex:    /* number, optional */,4    pageSize:     /* number, optional */,5    templateName: /* string, required */,6    query:        /* query.Query object */7});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idstringWorkbook query ID.
options.pageIndexnumberoptionalPage index.
options.pageSizenumberoptionalPage size. The minimum value is 5, and the maximum value is 1000.
options.templateNamestringrequiredName of the results iterator variable referred to in the template.
options.queryquery.Query objectWorkbook query definition.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for addQuery