mynt

module function · N/render

bom()

render.bom(options)

Creates a PDF or HTML file object containing a bill of materials.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
render.bom(options)
Module
N/render
Returns
file.File
Governance
10 units
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1render.bom({2    entityId:     /* number, required */,3    printMode:    /* string, optional */,4    inCustLocale: /* boolean, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.entityIdnumberrequiredThe internal ID of the transaction associated with the bom.
options.printModestringoptionalThe print output type. Use the render.PrintMode enum to set this value. By default, uses the company/user preference for print output.
options.inCustLocalebooleanoptionalApplies when advanced templates are used. Print the document in the customer's locale. If basic printing is used, this parameter is ignored and the transaction form is printed in the customer's locale.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for bom