module function · N/workbook
createTableColumn()
workbook.createTableColumn(options)
Creates a table column.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createTableColumn({2 alias: /* string, optional */,3 condition: /* workbook.ConditionalFilter, optional */,4 label: /* string | workbook.Expression, optional */,5 sort: /* workbook.Sort, optional */,6 width: /* number, optional */7});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.alias | string | optional | The alias for the table column. The alias can be used for mapping results. |
| options.condition | workbook.ConditionalFilter | optional | Additional conditions for the table column. |
| options.label | string | workbook.Expression | optional | The label for the table column. |
| options.sort | workbook.Sort | optional | The sorting behavior for the table column. |
| options.width | number | optional | The width of the table column in the UI, in pixels. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createTableColumn(options) today. How should it read?
C
community proposals
Competing syntax for createTableColumn, 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?