module function · N/workbook
createTable()
workbook.createTable(options)
Creates a table view.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createTable({2 columns: /* workbook.TableColumn [], required */,3 dataset: /* dataset.Dataset, required */,4 id: /* string, required */,5 name: /* string | workbook.Expression, required */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.columns | workbook.TableColumn [] | required | The columns to include in the table view. |
| options.dataset | dataset.Dataset | required | The dataset containing the columns to include in the table view. |
| options.id | string | required | The ID of the table view. |
| options.name | string | workbook.Expression | required | The name of the table view. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createTable(options) today. How should it read?
C
community proposals
Competing syntax for createTable, 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?