mynt

module function · N/render

xmlToPdf()

render.xmlToPdf(options)

Passes XML to the BFO tag library (which is stored by NetSuite), and returns a PDF file.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
render.xmlToPdf(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.xmlToPdf({2    xmlString: /* xml.Document | string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.xmlStringxml.Document | stringrequiredThe XML document or string to convert to PDF. For information and examples about using BFO tags to create this document or string, see the documentation for the corresponding SuiteScript 1.0 API, nlapiXMLToPDF(xmlstring) in SuiteScript 1.0 Documentation .
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for xmlToPdf