module function · N/workbook
create()
workbook.create(options)
Creates a workbook.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
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});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.charts | workbook.Chart [] | optional | The c |
| options.description | string | optional | The description of the workbook. |
| options.name | string | optional | The name of the workbook. |
| options.pivots | workbook.Pivot [] | optional | The pivots to include in the workbook. |
| options.tables | workbook.Table [] | optional | The tables to include in the workbook. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.create(options) today. How should it read?
C
community proposals
Competing syntax for create, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?