Sublist object method · N/ui/serverWidget
addButton()
Sublist.addButton(options)
Adds a button to a sublist.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objSublist.addButton({2 id: /* string, required */,3 label: /* string, required */,4 functionName: /* string, optional */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.id | string | required | The internal ID name of the button. The internal ID must be in lowercase and without spaces. |
| options.label | string | required | The label for the button. |
| options.functionName | string | optional | The function name to call when clicking this button. The function name must be the name of the method defined in a custom module client script. For examples, see N/currentRecord Samples . Important: Custom module client scripts with the specified function must be attached to the form. To learn more, see Form.clientScriptModulePath and Form.clientScriptFileId . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to Sublist.addButton(options) today. How should it read?
C
community proposals
Competing syntax for addButton, 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?