List object method · N/ui/serverWidget
addColumn()
List.addColumn(options)
Adds a column to a list.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objList.addColumn({2 id: /* string, required */,3 label: /* string, required */,4 type: /* string, required */,5 align: /* string, optional */6});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.id | string | required | The internal ID of this column. The internal ID must be in lowercase, contain no spaces. |
| options.label | string | required | The label for this column. |
| options.type | string | required | The field type for this column. Set this value using the serverWidget.FieldType enum. Note: Not all field types are supported. Check supported values in serverWidget.FieldType |
| options.align | string | optional | The layout justification for this column. Set this value using the serverWidget.LayoutJustification enum. The default value is LEFT . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to List.addColumn(options) today. How should it read?
C
community proposals
Competing syntax for addColumn, 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?