module function · N/workbook

create()

workbook.create(options)

Creates a workbook.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
workbook.create(options)
Returns
workbook.Workbook
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2020.2
call shapefrom Oracle's parameter table
1workbook.create({2    charts:      /* workbook.Chart [], optional */,3    description: /* string, optional */,4    name:        /* string, optional */,5    pivots:      /* workbook.Pivot [], optional */,6    tables:      /* workbook.Table [], optional */7});
Oracle reference for this method
ParameterTypeRequiredDescription
options.chartsworkbook.Chart []optionalThe c
options.descriptionstringoptionalThe description of the workbook.
options.namestringoptionalThe name of the workbook.
options.pivotsworkbook.Pivot []optionalThe pivots to include in the workbook.
options.tablesworkbook.Table []optionalThe tables to include in the workbook.
B

No Mynt syntax yet.

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

C

Competing syntax for create, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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/workbook · workbook.create(options)

Suggest syntax for create